Siproxd Users Guide
Prev | Chapter 6. Troubleshooting | Next

# 6.3. Siproxd crashes

If siproxd crashes, a stack back trace usually is helpful to me:

1. start siproxd in the debugger (daemonize set to 0):

   `$ gdb ./src/siproxd`

   `(gdb) set args -c /path/to/siproxd.conf`

   `(gdb) run`

2. reproduce the crash

3. use gdb to print the stack backtrace:

       (gdb) info thread
       ...
       (gdb) bt
       #0  0x400ec9ee in __select ()
       #1  0xbffff6f8 in ?? ()
       #2  0x804a5c2 in main (argc=3, argv=0xbffffc54) at siproxd.c:186
       #3  0x4005bcb3 in __libc_start_main (main=0x804a30c <main>, argc=3,
           argv=0xbffffc54, init=0x8049a08 <_init>, fini=0x804edac <_fini>,
           rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffc4c)
           at ../sysdeps/generic/libc-start.c:78
       (gdb)

4. copy-paste all the output and include it in your problem report.

Prev | Home | Next
Create a Debug Log | Up | Sample Configurations