Hi Joerg,
I was thinking about it, but what I did was so, well, unstructured,
that I was not too sure.
Anyway, I will try to come up with something and if it looks OK, I
will definitely update the page.
Regards,
Abhik.
On Dec 29, 2007 4:24 PM, Joerg Mayer <[EMAIL PROTECTED]> wrote:
> On Sat, De
On Sat, Dec 29, 2007 at 03:52:25PM +0400, Abhik Sarkar wrote:
> While debugging this, I came across a couple of very interesting pages
> in the Wiki:
> http://wiki.wireshark.org/PerPacketMemoryCorrupted
> http://wiki.wireshark.org/Development/Canary
> and learnt a few things!
>
> These pages are a
Just so everyone knows, the issue was not caused by the tvb*
functions, but by a very simple error in an ep_alloc call:
char_array = ep_alloc(sizeof(gchar)*26);
g_sprintf(char_array, "0C0504%04x%04x0804%04x%02x%02x",
port_rec->dst_port, port_rec->src_port,
Thanks Richard... I was merely trying out all the API functions to
achieve the end result. Anyway, I will try out various ways possible
until I have it working and then post a patch for review.
Thanks!
Abhik.
On Dec 27, 2007 6:26 PM, Richard van der Hoff <[EMAIL PROTECTED]> wrote:
> Abhik Sarkar
Abhik Sarkar wrote:
> Hello Everyone,
>
> Is there some clear documentation on when tvb_new_* functions may or
> may not be called. I keep getting per-packet data corrupt, and I
> suspect that I am using tvb_new_composite or tvb_subset at an
> incorrect place.
tvb_new_subset can be called wheneve
Hello Everyone,
Is there some clear documentation on when tvb_new_* functions may or
may not be called. I keep getting per-packet data corrupt, and I
suspect that I am using tvb_new_composite or tvb_subset at an
incorrect place.
What I am attempting to do is to take various fields from one PDU,
t
