Brian Oleksa wrote:
I was wondering if somebody can give me a hand here...
I can verify the tools, I can run setup.but when I build...I am
getting the following error:
C:\Python26\python.exe rdps.py print.ps ps.c
rm -f svnversion.h
perl make-version.pl
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/6581
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build
The Buildbot has detected a new failure of Windows-XP-Win64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-Win64/builds/987
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-win64
Build
Hi,
I get this crash in tshark when I build the latest svn on my OSX PPC:
Thread 0 Crashed:
0 libwireshark.0.dylib 0x02953a14 ep_alloc0 + 36 (emem.c:524)
1 libwireshark.0.dylib 0x0295d488 oid_string2subid +
120 (oids.c:791)
2 libwireshark.0.dylib
Graham
What is weird about the hole thing is that I kept my old sources in
tact just in case the new sources blow up (like they did).
I can still build the old sources using the current set up on this same
machine.
Plus I can also run verify tools with no problem with the new source
Hi,
On 24 jul 2009, at 11:33, Ulf Lamping ulf.lamp...@googlemail.com
wrote:
Jaap Keuter schrieb:
Hi,
What's wrong with 1.2.1?
Hi!
AFAIK, e.g. the following PROFINET stuff that is not part of it:
http://anonsvn.wireshark.org/viewvc?view=revrevision=29150
Brian Oleksa wrote:
Graham
I completely rebooted my machine (just to make sure I was not using the
same command prompt)...tried again (it chugged along for a while)...
then it broke. Remember...I am not even trying the 64 bit stuff yet.
All I am trying to do is check out the new source and
Gilmour, Scott wrote:
Graham,
Did you ever receive the memory.dmp file?
Thanks
Scott
It was Gianluca Varenni that was looking for the dump file.
--
Regards,
Graham Bloice
___
Sent via:Wireshark-dev mailing
Yesafter I do my perl commands in the cygwin window..I just leave it
open.
I leave the cygwin window open when I build the older source and it works.
Anyway.I did close it and it still crashed.
I am going to continue to plug away at this.
Thanks,
Brian
Graham Bloice wrote:
Brian
Brian Oleksa wrote:
Anyway.here is the error that I am getting:
perl perlnoutf.pl make-authors-short.pl ../AUTHORS AUTHORS-SHORT
24275 [main] perl 3980 child_copy: linked dll data write copy failed,
0xBD2000
..0xBD2370, done 0, windows pid 3980, Win32 error 487
Any ideas why
Hi Stig,
I just built r29187 on the PPC buildslave machine (manually) and did
[WiresharkPPC:~/Documents/wireshark] tuexen% ./tshark
Capturing on en0
0.00 Cisco_51:ae:3e - Spanning-tree-(for-bridges)_00 STP Conf.
Root = 32768/97/00:19:06:d0:46:00 Cost = 4 Port = 0x80cf
1.796043
Sorry, I didn't see the email with the crashdump 2 days ago...
It looks like the crash dump is corrupted. Can you please check if you have any
minidumps in c:\windows\minidump?
Have a nice day
GV
- Original Message -
From: Graham Bloice
To: Developer support list for Wireshark
Bill Meier wrote:
Another example: I note that viewvc assumes (or is configured to
assume) 8 character tabs stops when displaying Wireshark source
(http://anonsvn.wireshark.org/viewvc).
It looks like Viewvc just dumps everything into a pre/pre container
and lets the browser decide.
I've
GV,
The folder c:\windows\minidump is empty.
What should I do next?
Thanks
Scott
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Gianluca Varenni
Sent: Friday, July 24, 2009 11:16 AM
To: Developer support list for Wireshark
Subject: Re:
Try to enable the generation of minidumps:
1. in the start menu, right click on Computer and choose properties
2. click on advanced system settings on the left
3. In the Advanced tab, click on Startup and recovery settings
4. In the write debugging information panel choose small memory dump and
On Jul 24, 2009, at 8:44 AM, Gerald Combs wrote:
Visual C++ defaults to tabs for indentation with tab stops every 4
characters. I'm not sure if these settings can be overridden without
changing the user's global preferences.
Then perhaps the answer is indent with space characters, not tab
Gerald
I did a "rebase" like you suggestedand did a build and it
worked..!!
I get NO errors when I do a build.
HOWEVER
If I double click on the wireshark.exe file... I get this:
If I type in wireshark.exe on the command line... I get this:
One things after another.
Any
Hi GV,
I tried that and no information was in the minidumps folder.
Should I try a different version of WinPcap.
Thanks
Scott
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Gianluca Varenni
Sent: Friday, July 24, 2009 12:46 PM
To: Developer
With Wireshark 1.0.4 running on vista, I cannot see my WiFi card as a
capture interface though I can see my Ethernet card.
Is this a known issue? Or I might be doing sth wrong?
Many thanks,
Joshua
___
Sent via:
are you talking about Wireshark or Windows?
GV
- Original Message -
From: Gilmour, Scott
To: Gianluca Varenni ; Developer support list for Wireshark
Cc: winpcap-bugs2
Sent: Friday, July 24, 2009 11:18 AM
Subject: RE: [Winpcap-bugs] [Wireshark-dev] Windows 2008 Server
Yes, I do have one listed as Microsoft:
\Device\NPF_{7D4C2BA0-BCB3-47D6-8E5C-5D30946E8150}.
What does this tell? Is it the wifi card I have? Then why there is no
descriptive name like what we get on xp?
Thanks,
Joshua
On Fri, Jul 24, 2009 at 11:36 AM, Gianluca Varenni
I just looked and libwireshark.dll and wiretap-0.3.1.dll are in my
wireshark directory. (see errors below).
Why are they not being found..?
Any thoughts...?
Thanks,
Brian
Brian Oleksa wrote:
Gerald
I did a "rebase" like you suggestedand did a build and it
worked..!!
I get NO
Microsoft is the wireless adapter.
Native wifi adapters on Vista/Win7 have an Intermediate driver (from MS)
between their miniport driver and winpcap itself, and such IM driver traps the
request that WinPcap uses to get the name, returning just Microsoft.
Have a nice day
GV
- Original
Wiresharkers.
I got the latest wireshark source and I was able to successfully to
build it.
I was successfully able to build my dissector under this new build
(*using win32*).
What are the steps to make a win64 build of my dissector using the cross
compilers..??
Here is what I have
Are we going to fix it? There should be a way to get the device
name/description.
If there are multiple WiFi devices (or other network devices showing same
problem) on a same machine, currently it's hard to tell which one is which.
Thanks,
Joshua
On Fri, Jul 24, 2009 at 12:05 PM, Gianluca
25 matches
Mail list logo
