Wireshark-dev: Re: [Wireshark-dev] Wireshark 1.2.6 Run Time Error
From: "Maynard, Chris" <Christopher.Maynard@xxxxxxxxx>
Date: Thu, 25 Mar 2010 11:09:26 -0400
Please don't file a bug report for bugs in your own dissector.

You might try running tools/check*.pl on your dissector and closely examining the BASE_* and FT_* types you've used to be sure you're using valid types for the chosen BASE (Refer to README.developer for more information).  Invalid FT_'s seems to be a common problem lately.  Other than that, you might try using a debugger to step through your dissector to find out where it crashes.

- Chris


-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Balint Reczey
Sent: Thursday, March 25, 2010 7:16 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Wireshark 1.2.6 Run Time Error

Of course.
Please open a bug report at https://bugs.wireshark.org/bugzilla/, attach 
your dissector's source licensed under GPL as a patch and mark the patch 
for review. ;-)

Cheers,
Balint



Reddy Nagendra-GKTC37 wrote:
> Hi,
> 
> I am creating one new dissector, in that I used
> 
> dissector_add("tipc-payload.interface", CLMP_SM_INT, clmp_sm_handle);
> 
> Comiplation and Linking gone smooth ...
> 
> But when we ran WireShark, giving run time error.
> 
> "This application has requested the Runtime to terminate it an unusual 
> way ...."
> 
> Can any one help me regarding run time error.
> Thanks,
> NAG
> 


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and 
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.