Run under gdb (some shorthand instructions are in docs/FAQ). Of course, gdb is typically one of the culprits that changes the nitty gritty details of the threading model and so it won't ever fail...
The only way I can thing of would be a kernel debugger, which Linux doesn't have - either that or a true ICE/hardware debugging platform. -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > Mitesh P Choksi > Sent: Wednesday, September 01, 2004 2:25 PM > To: Burton M. Strauss III > Cc: [EMAIL PROTECTED] > Subject: RE: [Ntop] killed by SIGSEGV > > > Dear Burton, > > I did find a page that you have mentioned exactly the same thing. > > Please note that I am willing to use my system as a test environment to > find out the problem. If you can give me a few pointer on how do I handle > this situation. > > Are there any other debugging parameters that I can use to find out the > cause. Since this is happening on RedHat machines, it is possible to > happen on all machines with redhat installed and I would think it's better > to find resolve the issue. > > I can do little C debugging and on can at least read and understand error > messages. > > I hope to be of some help. > > Regards, > > Mitesh > > On Wed, September 1, 2004 7:06 pm, Burton M. Strauss III said: > > We've discussed this in the past - AFAIR nobody ever really figured out > > what > > RH means. There's no specific POSIX limitation, etc., but it could be > > that > > EL3 is finally enforcing whatever that warning means. > > > > I don't have EL3, so I can't test in that environment. > > > > -----Burton > > > >> -----Original Message----- > >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > >> Mitesh P Choksi > >> Sent: Tuesday, August 31, 2004 3:28 PM > >> To: [EMAIL PROTECTED] > >> Subject: [Ntop] killed by SIGSEGV > >> > >> > >> Dear All, > >> > >> I am having ntop dying in a few minutes of starting. > >> > >> I use WhiteBox Linux EL3 which is based on RedHat EL 3.0 > >> > >> dmesg after ntop dies shows the following: > >> application bug: ntop(20149) has SIGCHLD set to SIG_IGN but calls > >> wait(). > >> (see the NOTES section of 'man 2 wait'). Workaround activated. > >> device eth0 left promiscuous mode > >> > >> strace -p <pid> shows the following: > >> rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0 > >> rt_sigaction(SIGCHLD, NULL, {SIG_IGN}, 8) = 0 > >> nanosleep({10, 0}, 0xbfffb054) = -1 EINTR (Interrupted > >> system call) > >> +++ killed by SIGSEGV +++ > >> > >> I turned on debugging (-K) but don't get any hints from > >> /var/log/messages. > >> > >> I have tried googling but have not found any specific answer. I need to > >> know how to I go around troubleshooting current ntop problem. > >> > >> Thanking you in advance. > >> > >> Regards, > >> > >> Cyberdude Murli > >> Land of the Kilimanjaro > >> The World! > >> _______________________________________________ > >> Ntop mailing list > >> [EMAIL PROTECTED] > >> http://listgateway.unipi.it/mailman/listinfo/ntop > > > > > -- > > Cyberdude Murli > The World! > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
