Re: Interesting Magic # exception understood by the MS debugger...

2001-04-03 Thread Alexandre Julliard
"James Hatheway" <[EMAIL PROTECTED]> writes: > OK, I don't know too much about the internals of the WINE debugger, so > here goes. Is there a field for this already, or should I make a new > field in DBG_THREAD structure? (I think that seems like the right place > for it) Yep, you can add a fie

Re: Interesting Magic # exception understood by the MS debugger...

2001-04-03 Thread James Hatheway
> > and (B) should we support MS's hack somehow in the official tree? > > Yes, in the Wine debugger, which should store the name and simply > continue execution, just like the MSVC debugger does. OK, I don't know too much about the internals of the WINE debugger, so here goes. Is there a field f

Re: Interesting Magic # exception understood by the MS debugger...

2001-04-02 Thread Alexandre Julliard
"James Hatheway" <[EMAIL PROTECTED]> writes: > For now, I put the little hack I attached to this mail in my tree to > save my sanity. My question to the list is, (A) is there a way to name > threads in Linux/Unix (I don't think so, but of course I could be wrong) No, and we don't need that. >

Interesting Magic # exception understood by the MS debugger...

2001-04-02 Thread James Hatheway
Hi guys, I encountered something interesting while debugging a newer build of my application. I noticed that all of a sudden I was receiving approximately 10 new exceptions in the debugger on startup that I wasn't receiving before. After digging a little, I found out that the app coders were mak