Wireshark · Ethereal-dev: Re: [ethereal-dev] ethereal plugin (gryphon) on AIX-4.3.2

[Guy Harris <gharris@xxxxxxxxxxxx>]

> Ethereal seems to work, but it core-dumps when I try to enable the
> gryphon plugin. Here is the stack trace from the core:
> 
> # dbx /usr/local/bin/ethereal
> Type 'help' for help.
> reading symbolic information ...warning: no source compiled with -g
> 
> [using memory image in core]
> 
> Segmentation fault in ptrgl._ptrgl
> [/usr/local/lib/ethereal/plugins/0.8/shr.o] a
> t 0xd11cc2f8 ($t1)
> 0xd11cc2f8 (_ptrgl+0x38) 800c0000        lwz   r0,0x0(r12)

The panic on an "lwz" looks very suspiciously like the problems Craig
Rodrigues saw with GTK+ applications at one point; his fix was, I think,
to link "-lgtk" with "-lgdk" (check the lists of GTK+ mailing list
messages I sent out earlier - the discussion of this problem, and the
ultimate solution, are in there).

My *guess* is that there's some kind of problem with "proto_init()" in
"packet-gryphon.c" calling one of the routines in the main Ethereal
image, probably due to some kind of hellish dynamic linking problem; on
AIX, can a run-time-loaded shared library (i.e., one loaded with
"dlopen()") call, by name, routines in the program that loaded it?  If
so, do you have to do anything special to arrange that this can happen,
e.g. compiling the main program with special flags to that its symbols
(or some of its symbols) are exported?