Le 24/09/2010 05:12, Peter Urbanec a écrit :
On 24/09/10 06:43, Eric Pouech wrote:
sure send me the .exe+pdb (+source) I'll have a look at it
Source and binaries sent to Eric in private, so that the list isn't
polluted with megabytes of binaries. If anyone else is interested in
having a co
On 24/09/10 06:43, Eric Pouech wrote:
sure send me the .exe+pdb (+source) I'll have a look at it
Source and binaries sent to Eric in private, so that the list isn't
polluted with megabytes of binaries. If anyone else is interested in
having a copy, please let me know and I'll forward it in p
I'm happy to provide test source code, 64-bit and 32-bit binaries and
matching PDB files, if anyone is interested in looking at the issue.
sure send me the .exe+pdb (+source) I'll have a look at it
I only tested winedbg on 64bit with gcc
A+
--
Eric Pouech
"The problem with designing something
lto:winehq@urbanec.net]
Sent: Thursday, September 23, 2010 10:05 AM
To: wine-devel@winehq.org
Subject: Re: Debugging 64-bit Wine Apps with winedbg
On 23/09/10 06:51, Tom Grubbe wrote:
> problem seems to be getting any kind of stack trace information from
> the 64-bit winedbg. This used t
On 23/09/10 06:51, Tom Grubbe wrote:
problem seems to be getting any kind of stack trace information from
the 64-bit winedbg. This used to work with the 32-bit version of winedbg.
I can confirm that wine64 winedbg can not produce valid backtraces for
multi-threaded programs (.exe + .pdb) gen
Hi,
I'm not a winedbg expert but I think your mis-using it.
As it's your software, you can compile it from source and add debug info.
I know Visual Studio can create .pdb files but I don't know if winedbg
can use it.
Personally, I'm using gcc mingw with -g and that perfectly works.
The easies
Hello, we're the developers of a large 64-bit Windows application that uses
Wine 1.3.0 64-bit on Linux. When testing began we discovered several crashes
inside our windows code on startup and needed to debug them. But the problem
seems to be getting any kind of stack trace information from the