Hi Frank,
you have probably checked the usual things like access permissions on the
directories and shared library files. Even so, have you tried to use strace
(on linux) or truss (Solaris) to see what ethereal is doing?
E.g. "strace -o /tmp/ethereal.out ethereal" and then grep for
plugins in the output file. It will show you which directories is searching
for plugins and if opening and reading a plugin shared lib worked ok.
Something like this (on linux):
open("/usr/lib/ethereal/plugins/0.9.3",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or
directory)
open("/usr/local/lib/ethereal/plugins/0.9.3",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 4
open("/usr/local/lib/ethereal/plugins/0.9.3/cosnaming.so", O_RDONLY) = 5
open("/usr/local/lib/ethereal/plugins/0.9.3/coseventcomm.so", O_RDONLY) = 5
open("/usr/local/lib/ethereal/plugins/0.9.3/gryphon.so", O_RDONLY) = 5
open("/usr/local/lib/ethereal/plugins/0.9.3/mgcp.so", O_RDONLY) = 5
open("/home/bernd/.ethereal/plugins",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or
directory)
It might be something trivial, like an older ethereal binary being called
that is
getting the plugins you are seeing from another directory, or wrong access
permissions ...
If strace or truss don't show anything, it might be the dlopen failing for
some
other reason. I am not sure if it will show a warning or error message. What
platform are you on?
Cheers,
Bernd
Any idea what would cause a plugin to be present in say
/usr/local/lib/ethereal/plugins/0.9.3
after doing a make install (as root)
but not shown in the tools/plugins menu.
It looks the same as the other plugin present
in the same directory, and they appear in the menu.
A idl2eth user generated a plugin that compiled ok, and
we can see it in the right lib directory.
