Re: [Wireshark-dev] Fwd: Now Accepting Applications for Mentoring Organizations for GSoC 2013
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 www.google-menlange.com and send me your username. Hi Gerald, It is good ? you are found a backup admin for GSoC ? Regards, Original Message Subject:Now Accepting Applications for Mentoring Organizations for GSoC 2013 Date: Mon, 18 Mar 2013 12:00:42 -0700 From: Carol Smith car...@google.com Reply-To: google-summer-of-code-announce+own...@googlegroups.com To: Google Summer of Code Announce google-summer-of-code-annou...@googlegroups.com Hi all, We're pleased to announce that applications for mentoring organizations for Google Summer of Code 2013 are now being accepted [1]. If you'd like to apply to be a mentoring organization you can do so via Melange [2]. If you have questions about how to use Melange, please see our User's Guide [3]. Please note that the application period [4] closes on 29 March at 19:00 UTC [5]. We will not accept any late applications for any reason. [1] - http://google-opensource.blogspot.com/2013/03/mentoring-organization-applications-now.html [2] - http://www.google-melange.com [3] - http://en.flossmanuals.net/melange/ [4] - http://www.google-melange.com/gsoc/events/google/gsoc2013 [5] - http://goo.gl/xmQMJ Cheers, Carol -- You received this message because you are subscribed to the Google Groups Google Summer of Code Announce group. To unsubscribe from this group and stop receiving emails from it, send an email to google-summer-of-code-announce+unsubscr...@googlegroups.com. To post to this group, send email to google-summer-of-code-annou...@googlegroups.com. Visit this group at http://groups.google.com/group/google-summer-of-code-announce?hl=en. For more options, visit https://groups.google.com/groups/opt_out. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org ?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Fwd: Now Accepting Applications for Mentoring Organizations for GSoC 2013
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', '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
www.google-menlange.com and send me your username.
Hi Gerald,
It is good ? you are found a backup admin for GSoC ?
Regards,
Original Message
Subject:Now Accepting Applications for Mentoring Organizations for
GSoC 2013
Date: Mon, 18 Mar 2013 12:00:42 -0700
From: Carol Smith car...@google.com javascript:_e({}, 'cvml',
'car...@google.com');
Reply-To:
google-summer-of-code-announce+own...@googlegroups.comjavascript:_e({},
'cvml',
'google-summer-of-code-announce%2bown...@googlegroups.com');
To: Google Summer of Code Announce
google-summer-of-code-annou...@googlegroups.com javascript:_e({},
'cvml', 'google-summer-of-code-annou...@googlegroups.com');
Hi all,
We're pleased to announce that applications for mentoring organizations
for Google Summer of Code 2013 are now being accepted [1]. If you'd like
to apply to be a mentoring organization you can do so via Melange [2].
If you have questions about how to use Melange, please see our User's
Guide [3].
Please note that the application period [4] closes on 29 March at 19:00
UTC [5]. We will not accept any late applications for any reason.
[1]
-
http://google-opensource.blogspot.com/2013/03/mentoring-organization-applications-now.html
[2] - http://www.google-melange.com
[3] - http://en.flossmanuals.net/melange/
[4] - http://www.google-melange.com/gsoc/events/google/gsoc2013
[5] - http://goo.gl/xmQMJ
Cheers,
Carol
--
You received this message because you are subscribed to the Google
Groups Google Summer of Code Announce group.
To unsubscribe from this group and stop receiving emails from it, send
an email to
google-summer-of-code-announce+unsubscr...@googlegroups.comjavascript:_e({},
'cvml',
'google-summer-of-code-announce%2bunsubscr...@googlegroups.com');.
To post to this group, send email to
google-summer-of-code-annou...@googlegroups.com javascript:_e({},
'cvml', 'google-summer-of-code-annou...@googlegroups.com');.
Visit this group at
http://groups.google.com/group/google-summer-of-code-announce?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
___
Sent via:Wireshark-dev mailing list
wireshark-dev@wireshark.orgjavascript:_e({}, 'cvml',
'wireshark-dev@wireshark.org');
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.orgjavascript:_e({},
'cvml', 'wireshark-dev-requ...@wireshark.org');
?subject=unsubscribe
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Renaming some value-string API functions
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, don't forget about the *_ext interfaces here. Oh, and _all_ documentation / code samples, etc. I get the idea, but we're wondering into parser territory here. It might be a whole can-o-worms. Just my E0.02, Jaap ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] proposed graph_analysis.c change
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 address a problem with not being able to resize the panes. The second, superseding patch is a bit more extensive in that it completely eliminates the pane_callback function. I thought that I would point out that I have only tested the change on GTK+ 3 and not earlier versions, but didn't know how far back we're intending to support. Comments, accolades, brickbats welcome. :) Ed Well, GTK2 would be nice ;) Thanks, Jaap ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Renaming some value-string API functions
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: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8461#c12 Yes, sorry, forgot that it started on another bug. Besides what's written there, don't forget about the *_ext interfaces here. Oh, and _all_ documentation / code samples, etc. That's what global search+replace is for :) It won't pick up wiki articles but it should get README.dev and others. I get the idea, but we're wondering into parser territory here. It might be a whole can-o-worms. Not sure what you mean? Just renaming a few functions, nothing parser-related? Evan ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Renaming some value-string API functions
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 find the rationale here: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8461#c12 Yes, sorry, forgot that it started on another bug. Besides what's written there, don't forget about the *_ext interfaces here. Oh, and _all_ documentation / code samples, etc. That's what global search+replace is for :) It won't pick up wiki articles but it should get README.dev and others. I get the idea, but we're wondering into parser territory here. It might be a whole can-o-worms. Not sure what you mean? Just renaming a few functions, nothing parser-related? What I mean is that you already got/may get several requests for matching functions: - case sensitive / non-sensitive - ASCII / UTF-8 / UCS-2 - wildcards. Thanks, Jaap ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Renaming some value-string API functions
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? 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 Yes, sorry, forgot that it started on another bug. Besides what's written there, don't forget about the *_ext interfaces here. Oh, and _all_ documentation / code samples, etc. That's what global search+replace is for :) It won't pick up wiki articles but it should get README.dev and others. I get the idea, but we're wondering into parser territory here. It might be a whole can-o-worms. Not sure what you mean? Just renaming a few functions, nothing parser-related? What I mean is that you already got/may get several requests for matching functions: - case sensitive / non-sensitive - ASCII / UTF-8 / UCS-2 - wildcards. Ya, I (or somebody) needs to take a look at defining a scope for this and perhaps simplifying the API. For now just having consistent names will be a win. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Source Build using Mac OSX?
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 as build system, but it fails, because the correct lib path for glib2 is not inserted into the compile command. Has anyone a step-by-step guide on how to setup the build, or is this a cmake-build system bug in wireshark? kind regards, Roland ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Source Build using Mac OSX?
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 compile (Airpcap amongst those) On Lion (10.7) I use MacPorts (2.1.3 currently) and build the Gtk2 version with just ./autogen.sh ./configure make Mountain Lion might be different, of course (my 10.8 machine is offline right now), d ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Source Build using Mac OSX?
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 everything I can not compile (Airpcap amongst those) Using Xcode's command-line tools, autoconf/automake/libtool downloaded in source code form from the GNU project's server and installed (because Mountain Lion doesn't supply them), and the top-level macosx-setup.sh script to set up the necessary libraries and developer, I can compile. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] proposed graph_analysis.c change
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 of code to address a problem with not being able to resize the panes. The second, superseding patch is a bit more extensive in that it completely eliminates the pane_callback function. I thought that I would point out that I have only tested the change on GTK+ 3 and not earlier versions, but didn't know how far back we're intending to support. Comments, accolades, brickbats welcome. :) Ed Well, GTK2 would be nice ;) Ha! OK, that's a good start. I have verified it on Windows and two different Linux machines all using GTK 2.24, but don't have a good way to try it on other configurations. 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. I can't see why the pane_callback routine needs to exist at all and things seem to work just fine with it deleted as per my patch. Ed ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Possible misuse of match_strval_idx
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:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Possible misuse of match_strval_idx
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 contains 64 entries it seems so yes. Thanks, Jaap ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Source Build using Mac OSX?
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 process. It works with autotools, but doesn't with cmake. But is this not the whole point for cmake in the first place? Some of the things I noticed so far: * Disabling werror is a necessity, but not specific to Mac * -fexcess-precision=fast needs to be disabled for llvm-clang with XCode 4.3 in CMakeLists.txt * Wireshark segfaults in glib if run with macports version still installed on the system I'll send a patch regarding cmake support, as well as an updated version of that script, when I get around it. regards, Roland On Sat, Mar 23, 2013 at 7:54 PM, Guy Harris g...@alum.mit.edu wrote: 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 everything I can not compile (Airpcap amongst those) Using Xcode's command-line tools, autoconf/automake/libtool downloaded in source code form from the GNU project's server and installed (because Mountain Lion doesn't supply them), and the top-level macosx-setup.sh script to set up the necessary libraries and developer, I can compile. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Source Build using Mac OSX?
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 doing the whole thing without macport is strictly speaking a painful process. It works with autotools, but doesn't with cmake. What does it refer to here? Presumably not macosx-setup.sh, as that's a stand-alone script, and is neither run by the Makefile generated by the autotools nor by the Makefile generated by CMake. Whether it installs stuff needed by the autotools or CMake to configure Wireshark is up to the software it's installing, not by the script itself. Some of the things I noticed so far: * Disabling werror is a necessity, Disabling -Werror for what? If you're referring to Wireshark, rather than macosx-setup.sh, we build it on several platforms with -Werror; it builds just fine for me on Mountain Lion with -Werror. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Possible misuse of match_strval_idx
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 array index with value -1? Evan Unless gsm_a_dtap_msg_cc_strings contains 64 entries it seems so yes. Filed as bug #8517. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] proposed graph_analysis.c change
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. I can't see why the pane_callback routine needs to exist at all and things seem to work just fine with it deleted as per my patch. If expose event refers to window system expose events, as in I, the window system, did not save a copy of the pixels behind this portion of your window when some other window was dragged on top of it or came to the front and covered it, and that portion of your window is now exposed, so you're going to have to draw it all over again, then whether thing work without expose event callbacks may depend on whether the window system saves those copies and redraws the exposed part of the window for you or doesn't save them and requires the application to do so. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
