Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
apps:xfburn:start [2026/11/13 12:27] – [Introduction] Fix grammar epetrigliaapps:xfburn:start [2026/11/13 12:31] (current) – [Debugging] Sync Debugging section with project's README.md epetriglia
Line 122: Line 122:
 ===== Debugging ===== ===== Debugging =====
  
-If xfburn crashes, freezes, or somehow makes no progress for you, then you can +If xfburn crashes, freezes, or somehow makes no progress for you, then you can help greatly in debugging the problem. It does require you to build xfburn from the sources, and to install gdb. If you can handle that, here are the exact instructions: 
-help greatly in debugging the problem. It does require you to build xfburn from + 
-the sources, and to install gdb. If you can handle that, here are the exact +1. Rebuild xfburn with debugging support - grab the sources, and run: 
-instructions:+ 
 +   $ meson setup build 
 +   $ meson compile -C build
  
-1. Rebuild xfburn with debugging support - grab the sources, and run (you can update  
-   `-j4` to match your core count): 
-   ``` 
-   $ autoconf 
-   $ ./configure && make clean all -j4 
-   ``` 
 2. Enable core dumps, then run xfburn until it hangs, or crashes: 2. Enable core dumps, then run xfburn until it hangs, or crashes:
-   ```+
    $ ulimit -c unlimited; xfburn/xfburn 2>&1 | tee xfburn.output    $ ulimit -c unlimited; xfburn/xfburn 2>&1 | tee xfburn.output
-   ``` + 
-3. From another terminal, kill xfburn (only if it hasn't crashed already, of coures) +3. From another terminal, kill xfburn (only if it hasn't crashed already, of course) 
-   ```+
    $ kill -SEGV `pidof xfburn`     $ kill -SEGV `pidof xfburn` 
-   ``` + 
-4. Get a backtrace from the coredump: +4. Get a backtrace from the coredump (Note that sometimes the core.xxxxxx file is just called core, and that 32270 is just an arbitrary number which was the process id - yours will be different): 
-   ```+
    $ gdb xfburn/xfburn core.32270 --batch -ex 'thread apply all bt' > xfburn.backtrace    $ gdb xfburn/xfburn core.32270 --batch -ex 'thread apply all bt' > xfburn.backtrace
-   ``` + 
-   (Note that sometimes the core.xxxxxx file is just called core, and that 32270 is +    
-    just an arbitrary number which was the process id - yours will be different) +5. Open up a bug report at our [[:apps:xfburn:bugs|issue tracker]] for xfburn, and add both the xfburn.output and the xfburn.backtrace files to it. Done! There is no need to attach the core dump, as it is heavily system dependent.
-5. Open up a bug report at our [[:apps:xfburn:bugs|issue tracker]] for xfburn, and add +
-   both the xfburn.output and the xfburn.backtrace files to it. Done! +
-   There is no need to attach the core dump, as it is heavily system dependent.+
  
 [[|Back to Top]]    [[|Back to Top]]