...
(gdb) set args -u root -i eth0 @/etc/ntop.conf -K
(gdb) set follow-fork-mode child
(gdb) r
That should follow ntop through it's daemonizing process. Usually I just remove the daemonizing switch from the .conf file, however.
Inside gdb, you may also see it break on SIGPIPE ... that's something that just happens and can't be worked around, so if you see it, just type cont (continue) and it will continue... The bomb you are looking for is probably a SIGSEGV.
-----Burton
From: Todd Bushnell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 06, 2005 11:54 AM
To: [EMAIL PROTECTED]
Subject: RE: [Ntop-dev] ntop-3.2-0.fc2 crashes
Thanks for the guidance – sorry for not RTFM :-\
Forgive my gdb ignorance, but when I try running ntop via gdb using the faq instructions I’m unable to launch the browser (which I can do one time (before crashing) when I run ntop regularly). I then assumed that it was implied that we need to do a “run” in gdb after setting the arguments. When I try this I get the following:
[EMAIL PROTECTED] pts -={09:40/06-Dec-05}=-
<snip />
Tue Dec 6 09:45:52 2005 Initializing gdbm databases
Detaching after fork from child process 14763.
Program exited normally.
Am I doing something wrong?
Todd Michael Bushnell,
CISSP | Information Security
Manager
DemandTec, Inc. | 1
Circle Star Way, Suite 200 | San Carlos, CA 94070
tel | +1.650.226.4708
cell | +1.415.271.3771
fax | +1.650.556.1190
_______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
