Re: [Wireshark-dev] Fwd: Now Accepting Applications for Mentoring Organizations for GSoC 2013

2013-03-23 Thread Alexis La Goutte
On Mon, Mar 18, 2013 at 9:57 PM, Gerald Combs ger...@wireshark.org wrote: Google has opened up applications for mentoring organizations fro GSoC 2013. In order to complete the application we need someone to act as a backup admin. Any volunteers? If so, please sign up at

Re: [Wireshark-dev] Fwd: Now Accepting Applications for Mentoring Organizations for GSoC 2013

2013-03-23 Thread Roland Knall
Hi I could act as backup as well, if no one else steps up. I will also amend the wiki page today with my projects. Kind regards, Roland Am Samstag, 23. März 2013 schrieb Alexis La Goutte : On Mon, Mar 18, 2013 at 9:57 PM, Gerald Combs ger...@wireshark.orgjavascript:_e({}, 'cvml',

Re: [Wireshark-dev] Renaming some value-string API functions

2013-03-23 Thread Jaap Keuter
On 03/22/2013 09:35 PM, Evan Huus wrote: As proposed and discussed in bug #8467. Any objections? https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8467 Took some digging to find the rationale here: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8461#c12 Besides what's written there,

Re: [Wireshark-dev] proposed graph_analysis.c change

2013-03-23 Thread Jaap Keuter
On 03/23/2013 12:58 AM, Ed Beroset wrote: In working on fixing a bug today, I made a proposed change or two to graph_analysis.c. See https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7418 for the context. The first patch was a very conservative one that simply added a bit of code to

Re: [Wireshark-dev] Renaming some value-string API functions

2013-03-23 Thread Evan Huus
On Sat, Mar 23, 2013 at 7:29 AM, Jaap Keuter jaap.keu...@xs4all.nl wrote: On 03/22/2013 09:35 PM, Evan Huus wrote: As proposed and discussed in bug #8467. Any objections? https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8467 Took some digging to find the rationale here:

Re: [Wireshark-dev] Renaming some value-string API functions

2013-03-23 Thread Jaap Keuter
On 03/23/2013 01:50 PM, Evan Huus wrote: On Sat, Mar 23, 2013 at 7:29 AM, Jaap Keuter jaap.keu...@xs4all.nl wrote: On 03/22/2013 09:35 PM, Evan Huus wrote: As proposed and discussed in bug #8467. Any objections? https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8467 Took some digging to

Re: [Wireshark-dev] Renaming some value-string API functions

2013-03-23 Thread Evan Huus
On Sat, Mar 23, 2013 at 9:18 AM, Jaap Keuter jaap.keu...@xs4all.nl wrote: On 03/23/2013 01:50 PM, Evan Huus wrote: On Sat, Mar 23, 2013 at 7:29 AM, Jaap Keuter jaap.keu...@xs4all.nl wrote: On 03/22/2013 09:35 PM, Evan Huus wrote: As proposed and discussed in bug #8467. Any objections?

[Wireshark-dev] Source Build using Mac OSX?

2013-03-23 Thread Roland Knall
Hi Can someone point me in the right direction on how to build wireshark successfully using Mountain Lion? So far I am failing spectacularly. Using MacPorts for the necessary libraries and dev-dependencies, and deactivating everything I can not compile (Airpcap amongst those) I tried using cmake

Re: [Wireshark-dev] Source Build using Mac OSX?

2013-03-23 Thread David Arnold
On 23/03/2013, at 3:51 PM, Roland Knall wrote: Can someone point me in the right direction on how to build wireshark successfully using Mountain Lion? So far I am failing spectacularly. Using MacPorts for the necessary libraries and dev-dependencies, and deactivating everything I can not

Re: [Wireshark-dev] Source Build using Mac OSX?

2013-03-23 Thread Guy Harris
On Mar 23, 2013, at 7:51 AM, Roland Knall rkn...@gmail.com wrote: Can someone point me in the right direction on how to build wireshark successfully using Mountain Lion? So far I am failing spectacularly. Using MacPorts for the necessary libraries and dev-dependencies, and deactivating

Re: [Wireshark-dev] proposed graph_analysis.c change

2013-03-23 Thread Ed Beroset
Jaap Keuter wrote: On 03/23/2013 12:58 AM, Ed Beroset wrote: In working on fixing a bug today, I made a proposed change or two to graph_analysis.c. See https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7418 for the context. The first patch was a very conservative one that simply added a bit

[Wireshark-dev] Possible misuse of match_strval_idx

2013-03-23 Thread Evan Huus
Am I correct in thinking that in packet-gsm_a_dtap.c around line 6432, if match_strval_idx doesn't find a match then we will access invalid memory because idx will be used as an array index with value -1? Evan ___ Sent via:

Re: [Wireshark-dev] Possible misuse of match_strval_idx

2013-03-23 Thread Jaap Keuter
On 03/23/2013 10:07 PM, Evan Huus wrote: Am I correct in thinking that in packet-gsm_a_dtap.c around line 6432, if match_strval_idx doesn't find a match then we will access invalid memory because idx will be used as an array index with value -1? Evan Unless gsm_a_dtap_msg_cc_strings

Re: [Wireshark-dev] Source Build using Mac OSX?

2013-03-23 Thread Roland Knall
Hi Thanks for the script. Was what I was looking for. But, the thing is messed up. Fixated on static versions and download urls, for one thing. If something goes wrong during download, the whole process is started again. And doing the whole thing without macport is strictly speaking a painful

Re: [Wireshark-dev] Source Build using Mac OSX?

2013-03-23 Thread Guy Harris
On Mar 23, 2013, at 4:02 PM, Roland Knall rkn...@gmail.com wrote: Thanks for the script. Was what I was looking for. But, the thing is messed up. Fixated on static versions and download urls, for one thing. If something goes wrong during download, the whole process is started again. And

Re: [Wireshark-dev] Possible misuse of match_strval_idx

2013-03-23 Thread Evan Huus
On Sat, Mar 23, 2013 at 6:39 PM, Jaap Keuter jaap.keu...@xs4all.nl wrote: On 03/23/2013 10:07 PM, Evan Huus wrote: Am I correct in thinking that in packet-gsm_a_dtap.c around line 6432, if match_strval_idx doesn't find a match then we will access invalid memory because idx will be used as an

Re: [Wireshark-dev] proposed graph_analysis.c change

2013-03-23 Thread Guy Harris
On Mar 23, 2013, at 1:00 PM, Ed Beroset bero...@mindspring.com wrote: One thing still puzzling me is the comment in the (now elided) code for pane_callback which says repaint the comment area because when moving the pane position there are times that the expose_event_comments is not called.