From: "John S. Fine" <johnfine AT erols DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Inline Assembler/CWSDPR0 (Privileged instructions)
Date: Thu, 18 Mar 1999 16:50:50 -0500
Lines: 31
Message-ID: <36F1753A.3F6D@erols.com>
References: <7copjd$mp6$1 AT murdoch DOT acc DOT Virginia DOT EDU> <36f02ea0 DOT sandmann AT clio DOT rice DOT edu> <7crk74$5jl$1 AT murdoch DOT acc DOT Virginia DOT EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: DwKTxh0d0dItCmZpILdlVktuLJD9p9/OfHnDD0N32g8=
X-Complaints-To: abuse AT rcn DOT com
NNTP-Posting-Date: 18 Mar 1999 21:52:14 GMT
X-Mailer:  Mozilla 3.01 (Win95; U)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Clark L. Coleman wrote:

> >You aren't executing the ring 0 if you have the debugger loaded!  It
. . .
> OK, I recompiled without -g and ran the EXE without gdb.

  No, you need the copy compiled with -g, but run without gdb.

> Here is the register dump info:
> 
> Exiting due to signal SIGSEGV
. . .
> Call frame traceback EIPs:
> 0x00002585
> 0x00001833
> 0x000016a9
> 0x00003532
> 
> That's it. Someone asked for a "symify of the traceback" and I have no
> idea what that means.

  As soon as you get that register dump on the screen you
type  SYMIFY progname.exe
(replacing with the correct name).  It will read debug info from
the EXE and use it to modify the register dump right on your
screen.  That modified register dump is the starting point for
finding the problem  (post it here if it isn't obvious when you
see it).
-- 
http://www.erols.com/johnfine/
http://www.geocities.com/SiliconValley/Peaks/8600/