Re: [Wireshark-dev] Query Regarding debugging

2007-08-13 Thread Luis EG Ontanon
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

Re: [Wireshark-dev] Query Regarding debugging

2007-08-13 Thread Richard van der Hoff
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, d

Re: [Wireshark-dev] Query Regarding debugging

2007-08-13 Thread Graham Bloice
[EMAIL PROTECTED] wrote: > > > > Hi, > > If I want put some printf in c file, it is possible or not. > because I have changed in packet_umts_fp.c, after changing the file it > gives error at the time of decoding. > [Dissector bug, protocol FP: STATUS_ACCESS_VIOLATION: dissector accessed an > i

Re: [Wireshark-dev] Query Regarding debugging

2007-08-13 Thread Luis EG Ontanon
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. On 13-Aug-2007 19:28:23 ZE5B, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > Hi, >

[Wireshark-dev] Query Regarding debugging

2007-08-13 Thread vaibhav . agarwal
Hi, If I want put some printf in c file, it is possible or not. because I have changed in packet_umts_fp.c, after changing the file it gives error at the time of decoding. [Dissector bug, protocol FP: STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address] please tell how to d