RE: Assert in print.c get_field_data() creating PD ML file

I'm using a "real data" tvbuff.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Gilbert Ramirez
Sent: 02 June 2006 14:31
To: Ethereal development
Subject: Re: [Ethereal-dev] Assert in print.c get_field_data() creating PDML file

On what data is the tvbuff created? Is it a sub-set of a previous
tvbuff, or is it a "modification" (decompression, decryption) of
previous tvbuff data? I.e., are you using a "subset" tvbuff or a "real
data" tvbuff?

--gilbert

On 6/2/06, Howlett, James (James) <[email protected]> wrote:
>
>
>
>
> Hi,
>
>
>
> If I create a tvbuff, and do not use add_new_data_source(), but reference it
> in elements added to the proto tree; then I reach "g_assert_not_reached()"
> in get_field_data() in print.c when exporting to PDML. I'm currently using
> ethereal 0.99.0.
>
>
>
> Is there any good reason for this assert?
>
> By default I do not wish to use add_new_data_source() - it appears to add a
> significant amount of overhead, and since I am often using large captures
> any reduction in overhead is a good thing J
>
>
>
> BTW Within our company we've been using a modified version of ethereal as a
> replacement for commercial protocol analysers, for monitoring traffic within
> 3G networks. It makes the commercial analysers look very poor value for
> money.
>
> I need to look through the modifications I've made to some of the existing
> protocols, and contribute some of my changes (eg how 'connections' are
> tracked within SCCP and ALCAP). Not least because otherwise I'll just have
> to keep doing merges every time a new version is released.
>
>
>
> Cheers,
>
>
>
> James.
> _______________________________________________
> Ethereal-dev mailing list
> [email protected]
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
>
>
_______________________________________________
Ethereal-dev mailing list
[email protected]
http://www.ethereal.com/mailman/listinfo/ethereal-dev