TIP: Click on subject to list as thread! ANSI
echo: os2prog
to: John Cocula
from: Russell Coker
date: 1994-06-16 22:27:00
subject: Cset problem.

RC> gets raised at run time, here's the error I get when 
RC> running my program:
RC> 
RC> "Exception = 80010001 occurred at EIP = 1a67b."
RC> 
RC>    Now the child thread gets created and runs perfectly.  
RC> In every way my program is working as designed except for 
RC> that error message.

 JC> It couldn't possibly be the compiler issuing the trap?  Try this:
 JC> every time you run icc.exe, add the flag /Tl- .  Then see if the error
 JC> repeats.

  I'll try it.  But why would the compiler do that?  When the compiler is
pre-loaded it's in a totally different session and there should be no way
for my application to interfere with it.  Is Cset++ known to have bugs in
it's pre-loading?

  cya, and thanks for the suggestion.


--- Maximus/2 2.01wb

* Origin: Multi - 61-3-739-7145 (3:633/363)
SEEN-BY: 54/54 620/243 632/301 348 365 386 998 633/104 252 260 357 363 371
SEEN-BY: 633/373 634/384 635/210 502 503 636/100 638/100 640/820 690/660
SEEN-BY: 711/409 413 430 807 808 809 934 712/353 623 713/888 800/1 2442/0
@PATH: 633/363 260 371 635/503 632/348 711/409 54/54 711/808 809 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.