>>>>> On Tue, 03 Jan 2006 14:58:51 +0100, Wolfgang Denk <[EMAIL PROTECTED]> >>>>> said:
W> In message <[EMAIL PROTECTED]> you wrote: >> W> Any ideas what might go wrong? >> >> This is a bug in strace I think. Try using gdb instead of strace. W> Hm... I see this: W> (gdb) run -f -c /etc/bacula/bacula-sd.conf W> Starting program: /usr/local/src/bacula/src/stored/bacula-sd -f -c /etc/bacula/bacula-sd.conf W> Reading symbols from shared object read from target memory...done. W> Loaded system supplied DSO at 0x13a000 W> [Thread debugging using libthread_db enabled] W> [New Thread -1208817984 (LWP 6934)] W> Detaching after fork from child process 6937. W> [New Thread -1210917968 (LWP 6938)] W> [New Thread -1221407824 (LWP 6939)] W> Detaching after fork from child process 6940. W> Detaching after fork from child process 6950. W> [New Thread -1231897680 (LWP 6962)] W> On the console the last message I see is this (then it hangs forever): W> Connecting to Storage daemon File at diddl.denx.de:9103 W> Any idea what to look for? Strange -- originally you said that it core dumped, so running it under gdb should have caused gdb to catch that. Or was the core dump only from strace? Anyway, you can send Ctrl-c to the gdb to wake it up and then try thread apply all bt which should show which thread is hanging and where. __Martin ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
