Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows XP x86

2014-05-05 Thread Evan Huus
I'm really not sure what's causing the wmem test suite to hang like this (and only on XP...) - the lack of additional output from the buildbot is confusing. Gerald, is this easily reproducible if you run ./wmem_test directly on the XP bot? On Mon, May 5, 2014 at 9:07 AM,

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows XP x86

2014-05-05 Thread Gerald Combs
The XP buildbot had quite a few error dialogs open complaining about a runtime error in wmem_test.exe. I closed them and it appears to run fine now. Process Explorer didn't show any unusual memory usage when I ran the test by hand. On 5/5/14 6:14 AM, Evan Huus wrote: I'm really not sure what's

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows XP x86

2014-05-05 Thread Evan Huus
I guess the original out-of-memory failures must have left it in a bad state or something. Thanks for taking a look. Evan On Mon, May 5, 2014 at 1:38 PM, Gerald Combs ger...@wireshark.org wrote: The XP buildbot had quite a few error dialogs open complaining about a runtime error in

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-06-22 Thread Evan Huus
Running ./wmem_test --verbose --seed=R02S7c3c1e743f8aa20695f4377c8b1c40c8 Should produce exactly the same run (with the same output and hopefully the same crash) as the buildbot saw. On Fri, Jun 21, 2013 at 1:33 AM, Graham Bloice graham.blo...@trihedral.com wrote: OK for me also on XP x32,

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-06-22 Thread Pascal Quantin
Hi Evan, I could not reproduce it either on my Windows XP box. Regards, Pascal. 2013/6/22 Evan Huus eapa...@gmail.com Running ./wmem_test --verbose --seed=R02S7c3c1e743f8aa20695f4377c8b1c40c8 Should produce exactly the same run (with the same output and hopefully the same crash) as the

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-06-22 Thread Evan Huus
Thanks for testing it, this is very odd... On Sat, Jun 22, 2013 at 11:33 AM, Pascal Quantin pascal.quan...@gmail.com wrote: Hi Evan, I could not reproduce it either on my Windows XP box. Regards, Pascal. 2013/6/22 Evan Huus eapa...@gmail.com Running ./wmem_test --verbose

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-06-21 Thread Graham Bloice
OK for me also on XP x32, although I'm not sure how to feed in the seed from the failing test run. Graham On 20 June 2013 16:56, Pascal Quantin pascal.quan...@gmail.com wrote: Failed to reproduce it on my side also, but I was running on Windows 7 x64. I will not have access to my XP x32 box

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-06-20 Thread Evan Huus
I am unable to reproduce even with the random seed listed in the output (./wmem_test --seed=R02S7c3c1e743f8aa20695f4377c8b1c40c8). Valgrind shows no errors. Is anybody else seeing misbehaviour here? Thanks, Evan On Thu, Jun 20, 2013 at 4:40 PM, buildbot-no-re...@wireshark.org wrote: The

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-03-17 Thread Evan Huus
These are still happening occasionally. I dug out my XP-32 virtualbox instance but have not been able to reproduce. Tangentially, running the test suite from cygwin I get the following failure (after the test the build-bot keeps failing on): 5 Suite: Unit tests 5.1 Step: exntest

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-03-17 Thread Bill Meier
On 3/17/2013 10:30 AM, Evan Huus wrote: These are still happening occasionally. I dug out my XP-32 virtualbox instance but have not been able to reproduce. Tangentially, running the test suite from cygwin I get the following failure (after the test the build-bot keeps failing on): 5 Suite:

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-03-17 Thread Bill Meier
On 3/17/2013 11:00 AM, Bill Meier wrote: Basically: You have to setup the Windows cmd environment so that MSVC can be invoked from the command line. (nmake, etc) (When you then run cygwin bash to run the test scripts nmake etc will be available). For instance: in my Windows cmd line setup

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-03-17 Thread Evan Huus
I'm still not having any luck (and I've reread https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html to no avail). I have two shells available: cygwin's bash and windows' cmd.exe. If I run cmd.exe and then run the vcvars32 script, I can build Wireshark correctly using nmake. This

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-03-17 Thread Bill Meier
On 3/17/2013 12:09 PM, Evan Huus wrote: I'm still not having any luck (and I've reread https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html to no avail). I have two shells available: cygwin's bash and windows' cmd.exe. If I run cmd.exe and then run the vcvars32 script, I can build

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-03-17 Thread Dirk Jagdmann
I'm still not having any luck (and I've reread https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html to no avail). I have two shells available: cygwin's bash and windows' cmd.exe. If I run cmd.exe and then run the vcvars32 script, I can build Wireshark correctly using nmake.

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-03-17 Thread Ed Beroset
-Original Message- From: Evan Huus eapa...@gmail.com Sent: Mar 17, 2013 12:09 PM To: Developer support list for Wireshark wireshark-dev@wireshark.org Subject: Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86 I'm still not having any

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-03-17 Thread Evan Huus
failure in Wireshark (development) on Windows-XP-x86 I'm still not having any luck (and I've reread https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html to no avail). I have two shells available: cygwin's bash and windows' cmd.exe. If I run cmd.exe and then run the vcvars32 script, I

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-02-25 Thread Evan Huus
This has been failing for a while now, but I am unable to reproduce (though I don't have exactly XP x86). Anybody got a VM kicking around who can figure out what's going on here? On Mon, Feb 25, 2013 at 10:44 PM, buildbot-no-re...@wireshark.org wrote: The Buildbot has detected a new failure on

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2013-02-25 Thread Gerald Combs
It seemed to start shortly after I added software updates. Unfortunately I'm traveling and haven't had a chance to look into it closely. On 2/26/13 11:52 AM, Evan Huus wrote: This has been failing for a while now, but I am unable to reproduce (though I don't have exactly XP x86). Anybody got a

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-08-19 Thread Evan Huus
The XP-x86 buildbot has been failing sporadically for over a week now. It seems to have started around revision 44359, but the actual cause could be any number of revisions on either side (I don't have an XP box to bisect with). Anyone have an idea what's happening? On Sun, Aug 19, 2012 at 11:22

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-19 Thread Guy Harris
On Feb 18, 2012, at 4:32 PM, Guy Harris wrote: We should probably build a libcliui static library from the stuff in ui/cli. (And we should probably move dftest.c out of ui/cli; either all the non-GUI commands should have their sources in there or none of them should.) OK, I've done that

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-18 Thread Guy Harris
On Feb 17, 2012, at 7:34 AM, Jeff Morriss wrote: I've been a little uneasy with the fact that there's no makefile in ui/ . We now have a makefile there; it builds a libui static library from ui/util.c. That library is linked with programs that need stuff from ui/util.c. We'll see if that

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-18 Thread Guy Harris
On Feb 18, 2012, at 4:10 PM, Guy Harris wrote: On Feb 17, 2012, at 7:34 AM, Jeff Morriss wrote: I've been a little uneasy with the fact that there's no makefile in ui/ . We now have a makefile there; it builds a libui static library from ui/util.c. That library is linked with programs

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-18 Thread Guy Harris
On Feb 18, 2012, at 4:11 PM, Guy Harris wrote: cd .. cd ui/win32 C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\nmake.exe / /f Makefile.nmake libgtkui_win32.lib Microsoft (R) Program Maintenance Utility Version 9.00.21022.08 Copyright (C)

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-18 Thread Guy Harris
On Feb 18, 2012, at 4:16 PM, Guy Harris wrote: In other Makefiles the libui_win32.lib library was renamed to libgtkui_win32.lib (as a result of a search-and-replace, but as that library is GTK+-specific, the rename makes sense), but it wasn't done in ui/win32/Makefile.nmake. I checked in

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Joerg Mayer
On Fri, Feb 17, 2012 at 04:49:37AM -0800, buildbot-no-re...@wireshark.org wrote: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/209 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason: scheduler Build Source

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Graham Bloice
-Original Message- Subject: Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86 On Fri, Feb 17, 2012 at 04:49:37AM -0800, buildbot-no-re...@wireshark.org wrote: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Graham Bloice
On Fri, Feb 17, 2012 at 04:49:37AM -0800, buildbot-no-re...@wireshark.org wrote: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/2 09 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason:

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Ed Beroset
Graham Bloice wrote: Most likely it has a problem with the / instead of \ in uil/util.obj. Does someone have an idea how to resolve this? util.obj is being produced in the top level root directory, but the linker is looking for it in ui\. I'm looking at the makefile now. Hmm. I think

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Joerg Mayer
On Fri, Feb 17, 2012 at 02:01:05PM -, Graham Bloice wrote: Most likely it has a problem with the / instead of \ in uil/util.obj. Does someone have an idea how to resolve this? util.obj is being produced in the top level root directory, but the linker is looking for it in ui\.

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Jeff Morriss
Ed Beroset wrote: Graham Bloice wrote: Most likely it has a problem with the / instead of \ in uil/util.obj. Does someone have an idea how to resolve this? util.obj is being produced in the top level root directory, but the linker is looking for it in ui\. I'm looking at the makefile now.

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Graham Bloice
On Fri, Feb 17, 2012 at 02:01:05PM -, Graham Bloice wrote: Most likely it has a problem with the / instead of \ in uil/util.obj. Does someone have an idea how to resolve this? util.obj is being produced in the top level root directory, but the linker is looking for it in

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Jeff Morriss
Joerg Mayer wrote: On Fri, Feb 17, 2012 at 02:01:05PM -, Graham Bloice wrote: Most likely it has a problem with the / instead of \ in uil/util.obj. Does someone have an idea how to resolve this? util.obj is being produced in the top level root directory, but the linker is looking for it

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Ed Beroset
Jeff Morriss wrote: I've been a little uneasy with the fact that there's no makefile in ui/ . It seems like putting source files in there but no makefile is asking for trouble. But I haven't thought about it much. We have the same issue in ui/cli. Ed

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Joerg Mayer
On Fri, Feb 17, 2012 at 09:59:22AM -0500, Jeff Morriss wrote: Ed Beroset wrote: Graham Bloice wrote: Most likely it has a problem with the / instead of \ in uil/util.obj. Does someone have an idea how to resolve this? util.obj is being produced in the top level root directory, but the linker

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Joerg Mayer
On Fri, Feb 17, 2012 at 10:34:33AM -0500, Jeff Morriss wrote: Joerg Mayer wrote: On Fri, Feb 17, 2012 at 02:01:05PM -, Graham Bloice wrote: Most likely it has a problem with the / instead of \ in uil/util.obj. Does someone have an idea how to resolve this? util.obj is being produced in

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Graham Bloice
Most likely it has a problem with the / instead of \ in uil/util.obj. Does someone have an idea how to resolve this? util.obj is being produced in the top level root directory, but the linker is looking for it in ui\. I'm looking at the makefile now. Hmm. I think this would need

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Jeff Morriss
Joerg Mayer wrote: On Fri, Feb 17, 2012 at 09:59:22AM -0500, Jeff Morriss wrote: Ed Beroset wrote: Graham Bloice wrote: Most likely it has a problem with the / instead of \ in uil/util.obj. Does someone have an idea how to resolve this? util.obj is being produced in the top level root

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Guy Harris
On Feb 17, 2012, at 8:34 AM, Jeff Morriss wrote: Ed sent me an email off-list [not sure if that part was intentional or not] and said he got it working now--there was probably something residual messing up his build. Yes - I had the same issue after an svn update, but it cleared up after

Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86

2012-02-17 Thread Ed Beroset
Jeff Morriss wrote: Joerg Mayer wrote: On Fri, Feb 17, 2012 at 09:59:22AM -0500, Jeff Morriss wrote: Ed Beroset wrote: Graham Bloice wrote: Most likely it has a problem with the / instead of \ in uil/util.obj. Does someone have an idea how to resolve this? util.obj is being produced in the