[Wireshark-dev] [PATCH][RFC] show number of segments which were used in the desgementation

2010-03-01 Thread Kaul
Attached non-elegant patch shows, in addition to the already shown total number of bytes, the number of segments that were used to desegment a message. It may not be very efficient (and I'm open to suggestions on how to enhance it) but it works. diff against SVN r32082. TIA, Y. reassemble.c.dif

Re: [Wireshark-dev] [Wireshark-commits] rev 32006: /trunk/ /trunk/epan/: oids.c: Messages each time Wireshark/tshark started

2010-03-01 Thread Pascal Quantin
Hi 2010/2/26 Balint Reczey > Balint Reczey wrote: > > Balint Reczey wrote: > >> Bill Meier wrote: > Log: > Prevent potential crash in libsmi. > From: Vincent Bernat > >>> Since SVN #32006 was committed, the following messages appear when > >>> tshark and Wireshark are started.

Re: [Wireshark-dev] emem.c:732: failed assertion [sort-of-SOLVED]

2010-03-01 Thread Luis EG Ontanon
Yup, you're right, I did not consider the limit when I decided to use ep_alloc. Anyway getting the limit out from emem works too. BTW... In the patch... I just forgot to free the blocks :( --- emem.c.12010-03-01 20:59:15.0 +0100 +++ emem.c 2010-03-01 20:59:25.0 +0100 @@

Re: [Wireshark-dev] emem.c:732: failed assertion [sort-of-SOLVED]

2010-03-01 Thread Luis EG Ontanon
On Mon, Mar 1, 2010 at 4:48 PM, varname wrote: > Luis EG Ontanon wrote: >>> Don't know if it's the only way, but changing the limit to 10MB fixed it >>> for my situation. >> >> It might have worked it arround until an 11Mb request overflows it again. > > sure. That's why I wrote "for my situation"

Re: [Wireshark-dev] emem.c:732: failed assertion [sort-of-SOLVED]

2010-03-01 Thread didier
Hi, Le lundi 01 mars 2010 à 16:48 +0100, varname a écrit : > Luis EG Ontanon wrote: > >> Don't know if it's the only way, but changing the limit to 10MB fixed it > >> for my situation. > > > > It might have worked it arround until an 11Mb request overflows it again. > > sure. That's why I wrote "

Re: [Wireshark-dev] emem.c:732: failed assertion [sort-of-SOLVED]

2010-03-01 Thread varname
Luis EG Ontanon wrote: >> Don't know if it's the only way, but changing the limit to 10MB fixed it >> for my situation. > > It might have worked it arround until an 11Mb request overflows it again. sure. That's why I wrote "for my situation". I 'never' expect to have to allocate more than 10MB a

Re: [Wireshark-dev] emem.c:732: failed assertion [sort-of-SOLVED]

2010-03-01 Thread Luis EG Ontanon
On Mon, Mar 1, 2010 at 3:38 PM, varname wrote: > > just to follow up on this > > >> results in a failed assertion whenever http_media.len is rather large >> (I'm guessing larger than 5MB from the text of the assertion). The >> assertion itself: > > That was a typo, it's actually ~2.5MB, as its shi

[Wireshark-dev] How do I call the pkcs1 dissection from another dissector?

2010-03-01 Thread Kaul
find_dissector("pkcs-1") doesn't seem to be the correct way to do it. How do I do it? There's a PKCS1 blob I want the PKCS#1 dissector to dissect. How do I call it? I can create a TVB for it, of course. TIA, Y. ___ Sent via:

Re: [Wireshark-dev] emem.c:732: failed assertion [sort-of-SOLVED]

2010-03-01 Thread varname
just to follow up on this > results in a failed assertion whenever http_media.len is rather large > (I'm guessing larger than 5MB from the text of the assertion). The > assertion itself: That was a typo, it's actually ~2.5MB, as its shifted right by two positions. > The source (emem.c:731)

[Wireshark-dev] Problems installing wireshark on SUSE Linux Enterprise Server 10 SP2

2010-03-01 Thread Osis Ellen-MGIA0856
1. Tried to install and build wireshark, which said it required GTK+ 2.4 or later. 2. Installed gtk+2.18.7 which said it needed atk, pango, cairo 3. Installed pango which said it needed cairo 4. Installled cairo which said checking for cairo's PNG functions feature... configure: WARNING: Cou

[Wireshark-dev] (no subject)

2010-03-01 Thread Osis Ellen-MGIA0856
___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?s