Wireshark mailing list archives

What's wrong with 1.3?


From: David Aggeler <david_aggeler () hispeed ch>
Date: Thu, 12 Nov 2009 22:58:35 +0100



I'm facing things I can't really explain and it is driving me nuts.

I now have the latest 1.2 and the latest 1.3 SVNs in parallel use. with 
the exact same copy of packet-dcm.c.
In 1.2 things behave as expected (both with 1.2 and 1.3 version 
packet-dcm.c).

In 1.3 I had yesterday:
- Debugging problems in MSEE (function is terminated somewhere in the 
middle)
- Setting a simple int in a structure causes a crash (heap error)
I'd usually contribute this to accessing deallocated memory, but why 
does the same thing work in 1.2? I'd also say, that about two month ago, 
I did not see this in 1.3.

Today I get an a DISSECOTOR_ASSERT_NOT_REACHED in a super simple 
proto_tree_add_int_format()
tvb is 28670 bytes long, the offset is only 622 and I'd like to mark 4 
bytes.

Is this to be expected with coding work going on?

David

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe


Current thread: