From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5905 invoked by alias); 12 Mar 2003 22:42:27 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 5865 invoked from network); 12 Mar 2003 22:42:26 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 12 Mar 2003 22:42:26 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18tGoy-0005xo-00 for ; Wed, 12 Mar 2003 18:43:44 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18tEvY-0003ay-00 for ; Wed, 12 Mar 2003 17:42:24 -0500 Date: Wed, 12 Mar 2003 22:42:00 -0000 From: Daniel Jacobowitz To: GDB Patches Subject: Re: [offbyone RFC] Merge i386newframe Message-ID: <20030312224224.GB8247@nevyn.them.org> Mail-Followup-To: GDB Patches References: <3E6FAF64.7070304@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E6FAF64.7070304@suse.cz> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-03/txt/msg00291.txt.bz2 On Wed, Mar 12, 2003 at 11:06:28PM +0100, Michal Ludvig wrote: > Hi Andrew, > this patch is a merge of Mark's i386newframe-branch to your > offbyone-branch. It works quite well, unwinds through signal frames and > frameless functions, but still has some strange regressions that aren't > present in i386newframe branch. > > For example this program: > int var; > void foo () > { > var = 0x1234; > } > int main () > { > foo (); > return 0; > } > > Running it in the GDB: > (gdb) b main > Breakpoint 1 at 0x804832c: file tst.c, line 8. > (gdb) r > Starting program: tst > > Breakpoint 1, main () at tst.c:8 > 8 foo (); > (gdb) n > > Program exited normally. > (gdb) > > Why it didn't stop on "return 0" but exitted immediately instead? Did > you observe this behaviour in offbyone branch too, or is it caused by > this patch? It seems to have something to do with symbols, linetables, > ... but I can't see how it could be related to this patch. It doesn't > matter if I compile the program with stabs or dwarf2 debug info. Ideas? Hmm, what usually causes this for me is that the frame ID has changed between two stops in main (the one where the user types next and the one returning from foo). -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer