From owner-freebsd-bugs Sun Jan 6 16:50: 7 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 086F537B402 for ; Sun, 6 Jan 2002 16:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g070o1N62260; Sun, 6 Jan 2002 16:50:01 -0800 (PST) (envelope-from gnats) Date: Sun, 6 Jan 2002 16:50:01 -0800 (PST) Message-Id: <200201070050.g070o1N62260@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: k Macy Subject: Re: ptrace bug was Re: gnu/33262: gdb does not handle pending signals correctly when single stepping Reply-To: k Macy Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR gnu/33262; it has been noted by GNATS. From: k Macy To: Bruce Evans Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: ptrace bug was Re: gnu/33262: gdb does not handle pending signals correctly when single stepping Date: Sun, 6 Jan 2002 16:46:57 -0800 (PST) When can we get your fixes committed? Using gdb 5.1 (see below) they appear to completely solve the problem. > (3) "stepi" seems to work perfectly with these fixes > for (1) and (2), but > "next" rarely works. gdb apparently gets > confused about the temporary > breakpoints that it sets for "next". It gets > SIGTRAPs for them and > should remove them and continue with single > steps, but it leaves them > in and spins getting SIGTRAPs (and SIGALRMs in > the test program). This > is with gdb-4.18. > My experience with -CURRENT installed from today's snapshot: FreeBSD weizen.extendedsolutions.com 5.0-20020106-CURRENT FreeBSD 5.0-20020106-CURRENT #1: Sun Jan 6 16:22:13 PST 2002 root@goober.extendedsolutions:/usr/src/sys/i386/compile/HADES i386 is that with 4.18 next works until the sleep, but the sleep never returns. With 5.1 it works correctly, so as soon as FreeBSD upgrades to 5.1 one we can mark the bug fixed. If by lending a hand I can accelerate that process I would be happy to do the work, e.g. migrating freebsd-uthread.c, the kernel core debug functionality etc. a brief excerpt from 5.1: (gdb) n 60 i = 0; (gdb) n 62 j = 0; (gdb) 63 printf("milliseconds elapsed is %d\n", sk_msecs4); (gdb) milliseconds elapsed is 243 64 test_sleep(2); (gdb) 65 } (gdb) 60 i = 0; (gdb) 62 j = 0; (gdb) 63 printf("milliseconds elapsed is %d\n", sk_msecs4); __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message