Codeview problem under OS/2 2.0

Article View: comp.os.os2.programmer

Article #2054

Back to comp.os.os2.programmer Previous Next

#2054

From: Ilkka Kallio
Date: Wed, 14 Oct 1992 06:31

16 lines
1434 bytes

    I need to debug 16-bit OS/2 PM multithread software in OS/2  2.0. 
Currently I am using Microsoft Codeview (version 3.11), but when an 
error in my application causes  a  Segmentation  Violation,  Codeview 
seems to lose all stack information and I cannot tell where the crash 
occurred. All I get from codeview is "??? - illegal code" which means 
that the code segment it is trying to read is altogether wrong.  Just 
when I need the information most badly - it is not available!

    Why does Codeview not tell me where the program crashed? Why does 
it lose the stack information?  It  seems  to  me  that  the  segment 
registers have all been  corrupted?  Can  this  be?  Has  anyone  had 
similar difficulties? Is there any workaround for this? Are there any 
better solutions? Are there any other  16-bit  debuggers  that  would 
work better under OS/2 2.0? (The  effort  required  to  convert  this 
application to 32-bit would be too large, so any suggestions to  this 
effect would not be helpful).

Technical Details

Message-ID: <IKA.92Oct14083128@stekt.oulu.fi>

Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!news.funet.fi!ousrvr.oulu.fi!ousrvr!ika

Show Full Headers

Complete Article Headers

Newsgroups: comp.os.os2.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!news.funet.fi!ousrvr.oulu.fi!ousrvr!ika
From: ika@stekt.oulu.fi (Ilkka Kallio)
Subject: Codeview problem under OS/2 2.0
Message-ID: <IKA.92Oct14083128@stekt.oulu.fi>
Lines: 16
Sender: news@ousrvr.oulu.fi
Organization: University of Oulu, Dept. of EE, Finland
Distribution: comp.os.os2.programmer
Date: Wed, 14 Oct 1992 06:31:28 GMT