[Wireshark-dev] RFD: The Future of Memory Management in Wireshark

2012-10-18 Thread Evan Huus
TL;DR - Jakub recently proposed a few changes to emem [1]. While I think they are a very good idea, I believe that in the long term the current emem design has too many fundamental limitations to make it worth adapting for our future needs. I propose that it should be gradually deprecated in favour

Re: [Wireshark-dev] [Wireshark-commits] rev 45566: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-rdp.c

2012-10-18 Thread Maynard, Chris
> -Original Message- > From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev- > boun...@wireshark.org] On Behalf Of Martin Kaiser > Sent: Thursday, October 18, 2012 5:11 PM > To: wireshark-dev@wireshark.org > Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 45566: > /trunk/epa

Re: [Wireshark-dev] [Wireshark-commits] rev 45566: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-rdp.c

2012-10-18 Thread Martin Kaiser
Hi, Thus wrote Maynard, Chris (christopher.mayn...@gtech.com): > Recently, I found and fixed some of these problems, but obviously I > didn't catch them all. Are there any more thoughts about changing > tvb_length_remaining() and tvb_reported_length_remaining() to return 0 > instead of -1? it l

Re: [Wireshark-dev] r45615: Read the program name rather than hardcoding it

2012-10-18 Thread Guy Harris
On Oct 18, 2012, at 4:18 AM, Anders Broman wrote: > I changed most occurrences in the nsi installer of wireshark to > ${PROGRAM_NAME} and also in some places of > Makefile.nmake in error as it now seems. So at least as convention (on > windows) we used wireshark/Wireshark > (As file names ar

Re: [Wireshark-dev] Getting reports of Crashes on recent SVN builds

2012-10-18 Thread Anders Broman
Yes, I can't reproduce the crash after reverting r45511 Regards Anders -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Anders Broman Sent: den 18 oktober 2012 15:20 To: Developer support list for Wireshark Subject: R

Re: [Wireshark-dev] Getting reports of Crashes on recent SVN builds

2012-10-18 Thread Anders Broman
-Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jakub Zawadzki Sent: den 18 oktober 2012 15:13 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Getting reports of Crashes on recent SVN builds On

Re: [Wireshark-dev] Getting reports of Crashes on recent SVN builds

2012-10-18 Thread Jakub Zawadzki
On Thu, Oct 18, 2012 at 11:22:18AM +, Anders Broman wrote: > 1) Start capture on an interface > 2) Stop the capture > 3) Restart the capture > 4) Press "continue without saving" > 5) Wireshark dies at this moment Can you try reverting r45511? ___

Re: [Wireshark-dev] Getting reports of Crashes on recent SVN builds

2012-10-18 Thread Anders Broman
Ooops there is also System: Linux 2.6.27.42-0.1-pae #1 SMP 2010-01-06 16:07:25 +0100 i686 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Gilouche Memory status: size: 232710144 vsize: 232710144 resident: 7365427

[Wireshark-dev] Getting reports of Crashes on recent SVN builds

2012-10-18 Thread Anders Broman
1) Start capture on an interface 2) Stop the capture 3) Restart the capture 4) Press "continue without saving" 5) Wireshark dies at this moment Regards Anders ___ Sent via:Wireshark-dev mailing list Archives:http://

Re: [Wireshark-dev] r45615: Read the program name rather than hardcoding it

2012-10-18 Thread Anders Broman
-Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Guy Harris Sent: den 18 oktober 2012 10:13 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] r45615: Read the program name rather than hardcoding i

Re: [Wireshark-dev] Add date to release notes

2012-10-18 Thread Jaap Keuter
On 2012-10-18 11:17, Jakub Zawadzki wrote: On Thu, Oct 18, 2012 at 10:09:03AM +0100, Graham Bloice wrote: One way to see release dates is to query the svn repo (...) or check last modified date @ http://www.wireshark.org/download/src/all-versions/ Or check the wiki: http://wiki.wireshark.org

Re: [Wireshark-dev] Add date to release notes

2012-10-18 Thread Bálint Réczey
2012/10/18 Jakub Zawadzki : > On Thu, Oct 18, 2012 at 10:09:03AM +0100, Graham Bloice wrote: >> One way to see release dates is to query the svn repo (...) > > or check last modified date @ > http://www.wireshark.org/download/src/all-versions/ > > Stil I think it'd be good to have release dates in

Re: [Wireshark-dev] Add date to release notes

2012-10-18 Thread Jakub Zawadzki
On Thu, Oct 18, 2012 at 10:09:03AM +0100, Graham Bloice wrote: > One way to see release dates is to query the svn repo (...) or check last modified date @ http://www.wireshark.org/download/src/all-versions/ Stil I think it'd be good to have release dates in relnotes.

Re: [Wireshark-dev] Add date to release notes

2012-10-18 Thread Graham Bloice
> -Original Message- > From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev- > boun...@wireshark.org] On Behalf Of Evan Huus > Sent: 17 October 2012 17:57 > To: Wireshark Developer List > Subject: [Wireshark-dev] Add date to release notes > > I recently wanted to find out when a

Re: [Wireshark-dev] r45615: Read the program name rather than hardcoding it

2012-10-18 Thread Guy Harris
On Oct 18, 2012, at 12:51 AM, Anders Broman wrote: > From unistall.nsi > :Section /o "Un.Personal Settings" un.SecPersonalSettings > ;--- > SectionIn 2 > SetShellVarContext current > Delete "$APPDATA\${PROGRAM_NAME}\*.*" > RMDir "$APPDATA\${PROGRAM_NAME}"

Re: [Wireshark-dev] r45615: Read the program name rather than hardcoding it

2012-10-18 Thread Anders Broman
-Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Guy Harris Sent: den 18 oktober 2012 08:11 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] r45615: Read the program name rather than hardcoding i