Date: Sun, 19 May 2002 12:48:11 +0100
From: Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer: The Bat! (v1.60h) UNREG / CD5BF9353B3B7091
X-Priority: 2 (High)
Message-ID: <17244558826.20020519124811@softhome.net>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: Charles Sandmann <sandmann AT clio DOT rice DOT edu>, djgpp-workers AT delorie DOT com
Subject: Re[4]: emacs under w2k
In-Reply-To: <Pine.SUN.3.91.1020519130432.17558B-100000@is>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1020519130432 DOT 17558B-100000 AT is>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 May 2002 10:47:35.0057 (UTC) FILETIME=[95D13010:01C1FF22]
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> So it's calling our 16-bit helper.  That might explain why stepping into
> that call doesn't work.  Thus, this is one of the cases where I'd suggest 
> to set a breakpoint on the line following the lcall:

>    setc    %dl

> and type `continue'.

OK, I've followed your advice, and the problem (the old good abort,
not SIGTRAP, still seems to happen at lcall. So as far as falsiness
of this alert is concerned, only SIGTRAP is false...
-----
(gdb) nexti
0x00001405 in brk_common ()
1: x/i $eip  0x1405 <brk_common+85>:    lcall  *0x10f080
(gdb) disas 0x1405 0x1410
Dump of assembler code from 0x1405 to 0x1410:
0x1405 <brk_common+85>: lcall  *0x10f080
0x140b <brk_common+91>: setb   %dl
0x140e <brk_common+94>: pop    %eax
0x140f <brk_common+95>: int    $0x31
End of assembler dump.
(gdb) break *0x140b
Breakpoint 5 at 0x140b
(gdb) c
Continuing.
D:\devel\djgpp\gnu\emacs\src>
-----

What I don't get is how I supposed to look into code called by lcall?

Laurynas