Tee hee hee... You forgot the "run" command to start the program...  Of
course nothing happens :-)

After run, wait until ntop dies, then do the various info and bt full
commands...

-----Burton 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Aaron Grewell
Sent: Thursday, March 17, 2005 3:50 PM
To: [email protected]
Subject: RE: [Ntop] NTop dies on RHEL 4

On Thu, 2005-03-17 at 13:16 -0600, Burton Strauss wrote: 
> Run under gdb (instructions are in docs/FAQ at the end) and capture 
> the failure point information (threads, stacks, bt full etc.) 
> -----Burton

sudo gdb /usr/bin/ntop

GNU gdb Red Hat Linux (6.1post-1.20040607.62rh) Copyright 2004 Free Software
Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db
library "/lib/tls/libthread_db.so.1".

(gdb) set args -u root -K @/etc/ntop.conf

I ran 'list' several times after this, not sure what I was looking for.
Eventually it gave this output:

(gdb) list
Line number 595 out of range; main.c has 594 lines.

(gdb) info stack
No stack.

(gdb) print deviceId
No symbol "deviceId" in current context.

(gdb) help info thread
IDs of currently known threads.

(gdb) bt full
No stack.

I'm confused.  This doesn't look anything like what I expected.  Clearly
I've done something wrong here.
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop

_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to