Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread Anders Broman
From: Wireshark-dev On Behalf Of Maynard, Chris Sent: den 18 september 2018 15:55 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Unhandled exception >This particular crash with transum didn’t occur just by launching Wireshark >though, but only when reading a c

Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread Maynard, Chris
...@wireshark.org] On Behalf Of Anders Broman Sent: Tuesday, September 18, 2018 9:42 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Unhandled exception Hi, At the very least we should have a test step activating all protocols and starting the application. As they are disabled

Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread Anders Broman
2018 15:36 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Unhandled exception Thanks. Should the fuzz tester(s) enable all dissectors by default? If I “enable all protocols”, then currently the enabled_protos file lists these 3: prp, stcsig and transum. - Chris From

Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread Maynard, Chris
, September 18, 2018 4:26 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Unhandled exception https://code.wireshark.org/review/c/29715/ Cheers, Pascal. Le mar. 18 sept. 2018 à 10:22, Pascal Quantin mailto:pascal.quan...@gmail.com>> a écrit : I'm uploading a

Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread Anders Broman
: [Wireshark-dev] Unhandled exception Hi, Perhaps filter names referenced in other dissectors should be a define in a common .h file to make it obvious that the name must be changed in more than one place. Solving part of the problem. Then TRANSNUM should check for -1 I suppose and perhaps my trouble

Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread Anders Broman
.cn_call_id" }, { -1, "dcerpc.cn_ctx_id" }, { -1, "dns.id<http://dns.id>"}, }; Regards Anders -Original Message- From: Wireshark-dev mailto:wireshark-dev-boun...@wireshark.org>> On Behalf Of João Valverde Sent: den 18 september 2018 10:10 To: wiresha

Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread Pascal Quantin
;>> { -1, "udp.dstport" }, >>> { -1, "udp.stream" }, >>> { -1, "udp.length" }, >>> >>> { -1, "ssl.record.content_type" }, >>> >>> { -1, "tds.type" }, >>> { -1, "

Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread Pascal Quantin
{ -1, "smb.mid" }, >> >> { -1, "smb2.sesid" }, >> { -1, "smb2.msg_id" }, >> { -1, "smb2.cmd" }, >> >> { -1, "dcerpc.ver" }, >> { -1, "dcerpc.pkt_type" }, >> { -1, &qu

Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread Pascal Quantin
gth" }, > > { -1, "smb.mid" }, > > { -1, "smb2.sesid" }, > { -1, "smb2.msg_id" }, > { -1, "smb2.cmd" }, > > { -1, "dcerpc.ver" }, > { -1, "dcerpc.pkt_type" }, > { -1, "dcerpc.cn

Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread Anders Broman
esid" }, { -1, "smb2.msg_id" }, { -1, "smb2.cmd" }, { -1, "dcerpc.ver" }, { -1, "dcerpc.pkt_type" }, { -1, "dcerpc.cn_call_id" }, { -1, "dcerpc.cn_ctx_id" }, { -1, "dns.id"}, }; Regards Anders -

Re: [Wireshark-dev] Unhandled exception

2018-09-18 Thread João Valverde
", group=1, code=6) Thanks. - Chris -Original Message- From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Richard Sharpe Sent: Monday, September 17, 2018 4:22 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-d

Re: [Wireshark-dev] Unhandled exception

2018-09-17 Thread Maynard, Chris
v-boun...@wireshark.org] On Behalf Of Richard Sharpe Sent: Monday, September 17, 2018 4:22 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Unhandled exception CONFIDENTIALITY NOTICE: This message is the property of International Game Technology PLC and/or its subsi

Re: [Wireshark-dev] Unhandled exception

2018-09-17 Thread Richard Sharpe
On Mon, Sep 17, 2018 at 12:31 PM, Maynard, Chris wrote: > Hello, > > Recently I’ve begun seeing the following unhandled exception with master > when loading any capture file or attempting to capture on any interface – at > least that I tried, but I haven’t found any capture file or capture >

[Wireshark-dev] Unhandled exception

2018-09-17 Thread Maynard, Chris
Hello, Recently I've begun seeing the following unhandled exception with master when loading any capture file or attempting to capture on any interface - at least that I tried, but I haven't found any capture file or capture interface where this doesn't happen now: Unhandled exception

Re: [Wireshark-dev] Unhandled exception - uat_gui.c

2008-01-30 Thread Jaap Keuter
Hi, Shouldn't smi_modules_uat and smi_paths_uat be listed as 'DATA' items in libwireshark.def. Or is there something with WS_IMPORT? I don't really know how this stuff works in the Win32 domain. Thanx, Jaap Andrew Hood wrote: SVN at 24225 Windows XP Pro SP2 M$ Visual Studio 8.0

Re: [Wireshark-dev] Unhandled exception - uat_gui.c

2008-01-30 Thread Luis EG Ontanon
uat_t* uat_get_table_by_name(const char* name) { guint i; for (i=0; i all_uats-len; i++) { if ( g_strequal((g_ptr_array_index(all_uats,i))-name,name) ) { return (g_ptr_array_index(all_uats,i)); } }

Re: [Wireshark-dev] Unhandled exception - uat_gui.c

2008-01-30 Thread Jaap Keuter
Hi, I'm missing the point here. Is this a code snippet returning NULL that causes the failure? Is it a fix? For what? Maybe this should be filed in bugzilla and handled the regular way. Thanx, Jaap Luis EG Ontanon wrote: uat_t* uat_get_table_by_name(const char* name) { guint i;

Re: [Wireshark-dev] Unhandled exception - uat_gui.c

2008-01-30 Thread Luis EG Ontanon
Sorry, I thought I wrote that... Instead of trying to export the variables that point to the uats we should get the pointer by other means. The code snipplet was the means for that. L On Jan 30, 2008 10:40 PM, Jaap Keuter [EMAIL PROTECTED] wrote: Hi, I'm missing the point here. Is this a

Re: [Wireshark-dev] Unhandled exception - uat_gui.c

2008-01-30 Thread Andrew Hood
Luis EG Ontanon wrote: Sorry, I thought I wrote that... Instead of trying to export the variables that point to the uats we should get the pointer by other means. The code snipplet was the means for that. This works: In epan/libwireshark.def make smi_modules_uat and smi_paths_uat DATA as

Re: [Wireshark-dev] Unhandled exception - uat_gui.c

2008-01-30 Thread Stig Bjørlykke
2008/1/30, Luis EG Ontanon [EMAIL PROTECTED]: Instead of trying to export the variables that point to the uats we should get the pointer by other means. The code snipplet was the means for that. I have tried adding your function to uat.c and use this in nameres_prefs.c. But I'm currently

Re: [Wireshark-dev] Unhandled exception - uat_gui.c

2008-01-30 Thread Stig Bjørlykke
Seems to be working ok on win32 with r24229 :) -- Stig Bjørlykke ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev