[Guy Harris <guy@xxxxxxxxxx>]

> With any 802.11 capture file I try, this results in a seg fault,

No, it doesn't; that's a SIGABRT, which is raised when a piece of code
explicitly calls "abort()" to force a core dump, presumably because some
sanity check it was doing didn't find sanity (which is the case here).

> the stack trace of which is below.

	...

> Core was generated by `ethereal'.
> Program terminated with signal 6, Aborted.
> #0  0x403a6131 in __kill () from /lib/libc.so.6
> #0  0x403a6131 in __kill () from /lib/libc.so.6
> #1  0x403a5ead in raise (sig=6) at ../sysdeps/posix/raise.c:27
> #2  0x403a7534 in abort () at ../sysdeps/generic/abort.c:88
> #3  0x40254410 in g_logv () from /usr/lib/libglib-1.2.so.0
> #4  0x402544c7 in g_log () from /usr/lib/libglib-1.2.so.0
> #5  0x812d862 in process_node (proto_node=0x835c26c, 
>     parent_stat_node=0x835c244, ps=0x830d140, pkt_len=58)
>     at proto_hier_stats.c:89

Start up GDB again on that core dump, do "frame 5", and then do
"print *finfo" and "print *(finfo->hfinfo)", and report back the
results.