[Wireshark-dev] can't modify dissect_rrc_OCTET_STRING()

2008-06-11 Thread prakash chowbey
hi, im unable to modify dissect_rrc_OCTET_STRING()nbsp; function in packet-rrc..c , compiling after changing the rrc.cnf using nbsp;#.HDR or #.FTR is not getting reflected for this function, which ive used successfully to modify other asn genereted disssector functions. can anyone plz

Re: [Wireshark-dev] can't modify dissect_rrc_OCTET_STRING()

2008-06-11 Thread Kukosa, Tomas
Hi, which OCTET STRING type do you need to modify? It is not possibe to modify common OCTET STRING. You can use #.FN_HDR/BODY/FTR e.g. in following way: NAS-Message ::= OCTET STRING (SIZE (1..4095)) #.FN_HDR NAS-Message ... or e.g. RAB-Info-v6b0ext ::=SEQUENCE {

[Wireshark-dev] Tshark ver 0.99.6 crashed whole system 4th time while using display-filter option

2008-06-11 Thread Moheed Moheed Ahmad
Hi, I had a tshark built on version 0.99.6. My system mets serious crashes while running tshark using display filters and goes to *KGDB.* (crash is not consistent though, this time it was 4th crash). I couldn't get any core as system went to KGDB mode. Please let me know if it's known issue.

Re: [Wireshark-dev] can't modify dissect_rrc_OCTET_STRING()

2008-06-11 Thread Anders Broman
Hi. I'm not sure what you're trying to do but look at: InformationElements.asn: NAS-Message ::= OCTET STRING (SIZE (1..4095)) in .cnf #.FN_BODY NAS-Message VAL_PTR = nas_message_tvb tvbuff_t *nas_message_tvb=NULL; %(DEFAULT_BODY)s if (nas_message_tvb)

Re: [Wireshark-dev] can't modify dissect_rrc_OCTET_STRING()

2008-06-11 Thread Anders Broman
You probaly want: #.FN_HDR TargetRNC-ToSourceRNC-Container/dL-DCCHmessage Regards Anders prakash chowbey wrote: hi tomas, thanks for your reply i m stating what i want to do. in packet-rrc.c we have static const per_choice_t TargetRNC_ToSourceRNC_Container_choice[] = { { 0,

[Wireshark-dev] Return -1 from a heuristic dissector

2008-06-11 Thread Stig Bjørlykke
Hi all. The ms-mms dissector is returning -1 in some cases where it seems to want more data. The attached capture has no ms-mms data, and end up with a UDP packet not showing any Data. Shouldn't the ms-mms dissector return 0 or something? -- Stig Bjørlykke udp-pmul.pcap Description: Binary

Re: [Wireshark-dev] Return -1 from a heuristic dissector

2008-06-11 Thread Martin Mathieson
On Wed, Jun 11, 2008 at 3:04 PM, Stig Bjørlykke [EMAIL PROTECTED] wrote: Hi all. The ms-mms dissector is returning -1 in some cases where it seems to want more data. The attached capture has no ms-mms data, and end up with a UDP packet not showing any Data. Shouldn't the ms-mms dissector

Re: [Wireshark-dev] Tshark ver 0.99.6 crashed whole system 4th time while using display-filter option

2008-06-11 Thread Moheed Moheed Ahmad
Hi all, This time (5th time) system crashed without any filter option, so its not a filter issue. No core as system goes to kgdb. Regds, Moheed On Wed, Jun 11, 2008 at 3:20 PM, Moheed Moheed Ahmad [EMAIL PROTECTED] wrote: Hi, I had a tshark built on version 0.99.6. My system mets serious

Re: [Wireshark-dev] Ged125 protocol

2008-06-11 Thread Martin Corraine (mcorrain)
Hello, As someone told me, I should have my ged125 dissector be called by the TCP dissector. How do I go about doing this? Thanks, Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Guy Harris Sent: Tuesday, June 10, 2008 6:11 PM To: Developer

Re: [Wireshark-dev] Ged125 protocol

2008-06-11 Thread Tobias Wärre
dissector_add(tcp.port, portnumber, protocol_handle); It should be an example dissector in the README.developer that has this information. /Tobias -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Corraine (mcorrain) Sent: den 11 juni 2008 16:45

Re: [Wireshark-dev] Tshark ver 0.99.6 crashed whole system 4th time while using display-filter option

2008-06-11 Thread Richard van der Hoff
Moheed Moheed Ahmad wrote: Hi all, This time (5th time) system crashed without any filter option, so its not a filter issue. No core as system goes to kgdb. What's kgdb? This sounds more like an issue with your system rather than tshark. ___

Re: [Wireshark-dev] Tshark ver 0.99.6 crashed whole system 4th time while using display-filter option

2008-06-11 Thread Guy Harris
Moheed Moheed Ahmad wrote: My system mets serious crashes while running tshark using display filters and goes to *KGDB.* Then there's probably a bug either in the kernel or in some kernel loadable module. I'd suggest reporting this to MontaVista. It's possible, but *EXTREMELY* unlikely,

Re: [Wireshark-dev] Return -1 from a heuristic dissector

2008-06-11 Thread Martin Mathieson
On Wed, Jun 11, 2008 at 8:59 PM, Stig Bjørlykke [EMAIL PROTECTED] wrote: On 11. juni. 2008, at 16.22, Martin Mathieson wrote: Section 2.7.2 of README.developer suggests that it should return 0, since that's how many bytes it has dissected. It also shouldn't be setting desegment_len to

[Wireshark-dev] buildbot failure in Wireshark (development) on Solaris-10-SPARC

2008-06-11 Thread buildbot-no-reply
The Buildbot has detected a new failure of Solaris-10-SPARC on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Solaris-10-SPARC/builds/94 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: solaris-10-sparc Build

Re: [Wireshark-dev] Tshark ver 0.99.6 crashed whole system 4th time while using display-filter option

2008-06-11 Thread Moheed Moheed Ahmad
Hi, Sorry for the noise. Yes, the issue was with kernel in packet_recvmsg. Found and fixed. Thanks, Moheed On Wed, Jun 11, 2008 at 8:43 PM, Richard van der Hoff [EMAIL PROTECTED] wrote: Moheed Moheed Ahmad wrote: Hi all, This time (5th time) system crashed without any filter option,