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

[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 making use of a 'hidden' feature of MS VC that allowed
you to name your threads (thus allowing for easier debugging).

To do this, you call RaiseException with the code of 0x406D1388.
(Search on deja.com or google.com for "0x406D1388" for details.)
The windows debugger seems to be on the lookout for this code.  Of
course, what it does in wine is just breaking into the
debugger many times and getting on my nerves. :-)

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)
and (B) should we support MS's hack somehow in the official tree?


-James


--
James Hatheway
Software Designer - Macadamian Technologies, Inc.
james at macadamian.com ~ http://www.macadamian.com

  "Man könnte froh sein, wenn die Luft so rein wäre wie das Bier"
  "One could be happy if the air were as pure as the beer"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: name_thread.diff
Type: application/octet-stream
Size: 995 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20010402/f18361a6/name_thread.obj