Home page logo
/

wireshark logo Wireshark mailing list archives

Re: Getting a wireshark stack trace on Windows
From: "Speck, Michael AVL/DE" <Michael.Speck () avl com>
Date: Fri, 23 Aug 2013 06:36:41 +0000

Hi Evan,


basically you could use Microsoft's WinDbg, a free to use visual debugger. It is part of the Windows SDK, but could be 
installed as a standalone component by de-selecting all other features in the SDK installer. It could be downloaded 
from Microsoft's website at this URL: http://www.microsoft.com/whdc/devtools/debugging/default.mspx

There are two possibilities to debug a program:
1.) Start the debugger and choose "Open Executable..." from File menu to run the program in question under debugger 
control from beginning or
2.) configure the debugger as post-mortem debugger that will catch up after a program crashed. You'll find a 
description on how to setup this mode in the online help of WinDbg (search indexs for "postmortem")

In order to get a stack trace that contains function names instead of just some addresses you need debug symbols of the 
crashed program and the libraries it uses. That could either be in a separate file (*.pdb) or included inside the 
binary. Take care to properly configure symbol pathes (File -> Symbol File Path...). If debug symbols are not available 
for all resources wouldn't be a problem.


best regards
Michael



-----Original Message-----
From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Evan Huus
Sent: Donnerstag, 22. August 2013 21:02
To: Wireshark Developer List
Subject: [Wireshark-dev] Getting a wireshark stack trace on Windows

Could somebody who knows windows a little better take a look at bug #9062? I don't fully understand how our build 
environment interacts with windows debuggers / stack tracers. Is there a way to get a symbolic stack trace on Windows 
without compiling from source? Do the build-bot nightly packages include symbols?


Thanks,
Evan


https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9062

___________________________________________________________________________
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-request () wireshark org?subject=unsubscribe


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault