<br><br>
<div><span class="gmail_quote">2007/3/29, Dennis Schridde <<a href="mailto:devurandom@gmx.net">devurandom@gmx.net</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Am Donnerstag, 29. März 2007 schrieb Eric Pouech:<br>> Dennis Schridde a écrit :<br>> > Hello Wine users!
<br>> ><br>> > I've got a minidump from a ("real") Windows user of our game and would<br>> > like to extract information from it using winedbg.<br>> ><br>> ><br>> > The information winedbg gives me by default, is this:
<br>> ><br>> > [...]<br>> ><br>> > Which is pretty rare.<br>> > Via addr2line I can translate the backtrace to possibly valid locations<br>> > in our sourcefiles.<br>> ><br>> >
<br>> > My questions are:<br>> > - Why doesn't winedbg extract the sourcecode locations itself?<br>><br>> because it needs the original PE files (.exe, .dll) to get to the debug<br>> information<br>
> those files must be seated in directories listed in the _NT_SYMBOL_PATH<br>> environment variable<br>Maybe I am just doing it wrong, but<br>_NT_SYMBOL_PATH=. winedbg warzone2100.mdmp<br>doesn't change anything... (Even supplying the full path doesn't.)
<br>The exe (not all dlls, because I don't have a copy of the user's system) is of<br>course in the working directory.</blockquote>
<div> </div>
<div>But the debug info is not always in the .exe itself. the .exe can contain only a pointer to the debug info</div>
<div>what does 'winedbg -x debug -g warzone2100.exe' give ?</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">> > - Why doesn't winedbg show me the other information included in the<br>> > minidump, like the loaded modules, commandline options or version
<br>> > information?<br>><br>> 'info share' should do part of it... winedbg doesn't show the command<br>> line info nor options<br>That only shows me the memory ranges of some modules. The minidump includes
<br>more info, like the paths to dlls and similar. I am not sure whether it<br>includes version information, but it certainly contains the commandline used<br>to start the app.<br><br>> other thing you can do is to use winedump (man winedump)
<br>How do I do this? And what will it provide? I tried<br>winedump -G warzone2100.exe<br>but I have no idea what I shall do with that tremedously long and cryptic<br>list.</blockquote>
<div> </div>
<div>winedump warzone2100.mdmp</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">> > - How can I get the parameters to the last called function(s)?<br>><br>> see above for debug info
<br>If the general debug info worked, that would also show me the function<br>parameters?</blockquote>
<div> </div>
<div>yes</div></div><br>-- <br>Eric Pouech