Re: extracting info from a minidump via winedbg

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am Sonntag, 25. März 2007 schrieb Dennis Schridde:
> Hello Wine users!
>
> I've got a minidump from a ("real") Windows user of our game and would like
> to extract information from it using winedbg.
>
>
> The information winedbg gives me by default, is this:
> [...]
> Which is pretty rare.
> Via addr2line I can translate the backtrace to possibly valid locations in
> our sourcefiles.
>
>
> My questions are:
> - Why doesn't winedbg extract the sourcecode locations itself?
> - Why doesn't winedbg show me the other information included in the
> minidump, like the loaded modules, commandline options or version
> information? - How can I get the parameters to the last called function(s)?
I guess the lack of responses means that winedbg is not meant to be used for 
serious debugging?

--DS

Attachment: pgp6z3tbTF1LN.pgp
Description: PGP signature

_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users

[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux