On 10/2/06, Eric Pouech <[EMAIL PROTECTED]> wrote:
James Hawkins wrote:
> Auto = '1'
> Debugger = 'winedbg --auto %ld %ld'
>
does the attached patch help ?
[WineDbg]: fixed the auto mode
From: Eric Pouech <[EMAIL PROTECTED]>
I had to apply it by hand, but once I did it worked. Thanks Eric
James Hawkins wrote:
Auto = '1'
Debugger = 'winedbg --auto %ld %ld'
does the attached patch help ?
[WineDbg]: fixed the auto mode
From: Eric Pouech <[EMAIL PROTECTED]>
---
programs/winedbg/info.c |2 +-
programs/winedbg/tgt_active.c |6 +-
2 files changed, 6 insertions(+
On 10/2/06, Eric Pouech <[EMAIL PROTECTED]> wrote:
James Hawkins wrote:
> Hey guys,
>
> Since very recently, any time we get a crash in Wine, winedbg does not
> show a backtrace. This makes it significantly more difficult to debug
> the crash. Is anyone else experiencing this? I'll run a regr
James Hawkins wrote:
Hey guys,
Since very recently, any time we get a crash in Wine, winedbg does not
show a backtrace. This makes it significantly more difficult to debug
the crash. Is anyone else experiencing this? I'll run a regression
test as soon as I can.
what's the format of your A
On 10/2/06, James Hawkins <[EMAIL PROTECTED]> wrote:
Hey guys,
Since very recently, any time we get a crash in Wine, winedbg does not
show a backtrace. This makes it significantly more difficult to debug
the crash. Is anyone else experiencing this? I'll run a regression
test as soon as I can.
Hey guys,
Since very recently, any time we get a crash in Wine, winedbg does not
show a backtrace. This makes it significantly more difficult to debug
the crash. Is anyone else experiencing this? I'll run a regression
test as soon as I can.
wine: Unhandled page fault on read access to 0x0