Wireshark · Ethereal-dev: RE: [Ethereal-dev] problem in new dissector added

["Francisco Alcoba (TS/EEM)" <francisco.alcoba@xxxxxxxxxxxx>]

Hi,

 

Unless you have checked the option "update packet list in real time" the packets are dissected

only when the capture stops, so any problem the dissector has will show up then. The best way

to find out what is happening is, in my experience, to start ethereal in debug mode. You might

be using uninitialized pointers, incorrectly called functions, whatever; the fact that is shows in

the protocol list does not mean the dissector is 100% bug free.

 

I can only speak for myself, but I find it very difficult to understand code without knowing what it

is trying to do -in this case, without knowing what packet it is trying to dissect-. And, of course,

the more defined a problem is the easiest to offer suggestions -i.e. it is easier to suggest an

answer to "why in this line of code I use this function with this arguments and the result is not

what I expected" than to "why is my code not working?"-.

 

Regards,

 

  Francisco

-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx [mailto:ethereal-dev-bounces@xxxxxxxxxxxx]
Sent: martes, 05 de abril de 2005 18:22
To: ethereal-dev@xxxxxxxxxxxx
Subject: [Ethereal-dev] problem in new dissector added

Hello,
      I added new dissector. I already mailed that on forum but unable to get reply for that from anyone. I tried then to implement on my own and get successfully added to list of protocols(dont know whether its correct  implemented or not?).
      Curretly i am facing problem that when i try to capture packets, capture windows shows packet captured but when i stop it then accidently ethereal stops working giving segmentation fault. What is the reason i am getting segmentation fault?
        Hope this time i will get response from list.
Thanks in advance.
regards,
bunty.