[EMAIL PROTECTED] writes:
>
>
> On Fri, 16 Jun 2000, Uwe Bonnes wrote:
>
> > Hallo,
> >
> > running with --synchronous should give you a backtrace now.
> > The backtrace might be helpfull.
> >
> > Bye
> >
> > Uwe Bonnes [EMAIL PROTECTED]
> >
> > Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
> > --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
> >
> OK, winedbg will let me see a backtrace, which doesn't make much sense
> to me at first blush, but -- how am I meant to capture output from the
> debugger? Before it learned how to open its own xterm, I used script to
> capture the whole session, but that doesn't work any more.
>
../wine/documentation/winedbg gives an explanation.
Post the backtrace. perhaps someone can figure out.
> I like it that the debugger no longer runs me out of virtual memory
> loading symbols, I like the idea of dynamic debugmsg, but now I just
> want a text copy of the backtrace to run against the source and try to
> get oriented a bit.
>
> What does it mean that it is able to cont from the first DebugBreak
> without any more exceptions? Is this a timing/initialization race
> contition sort of thing, or do I not understand something fundamental?
I don't know.
Bye
Uwe Bonnes [EMAIL PROTECTED]
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
