--On Saturday, August 06, 2005 2:51 PM -0500 Burton Strauss
<[EMAIL PROTECTED]> wrote:
ntop uses the OS' standard facilities for finding it's executables and
library modules. This typically is . (current directory) + a bunch of
OS/distro specific locations (path for executables, library path for .so
files, etc.) So it may be that you have different ntop and libntopxxxx
files and are executing different ones depending upon where you run from.
One can use ldd to check libraries linked at load time. Do you log the
locations of libraries found dynamically after the program is started? That
can be used to check for libraries loaded from unexpected locations.
Another trick is to strace ntop and look at the paths of all files loaded.
I've done that with closed-source stuff (mostly commercial game server
binaries) to figure out its search rules.
But the best solution is still likely to be running under gdb (or its GUI
variations like ddd) to the crash and doing proper debugging.
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
