Wireshark-dev: Re: [Wireshark-dev] Query Regarding debugging
From: "Luis EG Ontanon" <[email protected]>
Date: Mon, 13 Aug 2007 17:10:51 +0200
On windows NULL and invalid-pointer dereferences take you to
packet-frame.c:312 where it shows the exception in the tree and keeps
going.

On *nix it just crashes.

On the other hand on win on some THROWS cause crashes as __except pops
the sigjmp  stack and then the END_TRY calls except_pop() on an empty
stack.

I been wandering and attempting various solutions without success for
this "bug on a bug handler".


On 8/13/07, Richard van der Hoff <[email protected]> wrote:
> Luis EG Ontanon wrote:
> > putting some printfs is possible (there are some issues on why you
> > might want to avoid it during protocol registration) but the Access
> > Violation is probably due to a NULL or ivalid pointer passed to
> > printf.
>
> [Dissector bug...] implies a wireshark-internal exception, does it not?
> (As opposed to a segfault.)
>
> Most likely thing is that it's not the printf at all, but a tvb_*
> function you are also calling, with bad arguments.
>
> _______________________________________________
> Wireshark-dev mailing list
> [email protected]
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>


-- 
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan

Propertarianism joined to capitalist vigor destroyed meaningful
commercial competition, but when it came to making good software,
anarchism won.
-- Eben Moglen