Hi,
What version are you trying to build?
What does the line
DOWNLOAD_PREFIX
In the file tools/win32-setup.sh say?
BR
Anders
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Sleep Less
Skickat: den 1 december 2006 09:43
Till: Developer support list
Hi,
thanks for the willingness to assist.
I did one thing : created an empty directory c:\wireshark-win32-libs
and then ran the nmake -f makefile.nmake all
with no further problems whatsoever.
Since my install was a clean one (no previous wireshark builds etc.)
I guess this may happen
[Apologies if this message appears twice - I am having some trouble persuading
exchange to be consistent about which SMTP address it uses for outgoing email,
and my first try bounced as a non-menber]
The wiki tips page has a couple of useful sections on debugging and setting up
browse
Thanks. Done all the wiki recommendations. I can now single/step debug main.c,
but as you can imagine, my interest lies deep in one of the dissectors - e.g.
packet-h263.c etc. How to I get to the situation I can single step through
those?
thanks
Douglas Pratley [EMAIL PROTECTED] wrote:
Thanks. Done all the wiki recommendations. I can now single/step debug main.c,
but as you can imagine, my interest lies deep in one of the dissectors - e.g.
packet-h263.c etc. How to I get to the situation I can single step through
those?
thanks
Douglas Pratley [EMAIL PROTECTED] wrote:
Well not quite - the compiler still disables breakpoint in the dissector, as it
fails to see
the (symbolic) connection. Methinks you need .bsc files for that, which MSVC
generates when you compile from the IDE, but apprently nmake does not.
any ideas?
Douglas Pratley [EMAIL PROTECTED]
The following works for me when debugging a plugin it should be the same
for a built in dissector:
1. Open wireshark.exe in MSVC and F5 to start debug.
2. When it pauses in ..\gtk\main.c press F5 again to continue Wireshark
startup.
3. Once you see the main display window open your dissector
An alternative way to do this is to:
1. Start wireshark.exe and msdev separately.
2. In MSDEV 6, choose menu Build - Start Debug - Attach to process
3. From the list of processes, choose wireshark.exe (most certainly one
of the topmost items).
4. Load the source file in which you would want to
It's the .pdb files that it needs - they should have been created when the file
was compiled. Is this a dynamically loaded plugin, or a statically linked
object? MSVC 6 can be a bit rubbish at putting breakpoints in dynamically
loaded code.
If you have MSCV 7.0 installed, you could try
Hi all
My company has given me some time to make a few improvements to
Wireshark and I was thinking of starting with the following feature:
Option to display time in seconds since epoch.
This looks fairly straightforward. Is anybody working on anything like
this already, or have
Douglas Pratley wrote:
This looks fairly straightforward. Is anybody working on anything like
this already, or have objections to the idea?
My only objection is that you presumably meant seconds and nanoseconds
since the epoch. :-)
Other than that, it should work.
Thanks for everyone's tips. I'm still stuck. PDB files do exist (we're talking
about the dissectors.lib segement since it aggregates the dissectors).
When I implement Douglas's method the breakpoints are not reached, and
Wireshark reports that the relevant dissector had a problem.
Douglas
On Fri, Dec 01, 2006 at 01:56:16PM -, Douglas Pratley wrote:
My company has given me some time to make a few improvements to
Wireshark and I was thinking of starting with the following feature:
Option to display time in seconds since epoch.
This looks fairly straightforward. Is anybody
On Dec 1, 2006, at 10:17 AM, Guy Harris wrote:
My only objection is that you presumably meant seconds and
nanoseconds
since the epoch. :-)
I.e. two packets that arrive 5 milliseconds apart should always have
different time stamps displayed, so the displayed time stamp should
have
14 matches
Mail list logo
