From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 01:48:44 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 493C416A419 for ; Mon, 8 Oct 2007 01:48:44 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: from smtpout05.prod.mesa1.secureserver.net (smtpout05-04.prod.mesa1.secureserver.net [64.202.165.221]) by mx1.freebsd.org (Postfix) with SMTP id 047F713C447 for ; Mon, 8 Oct 2007 01:48:43 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: (qmail 13158 invoked from network); 8 Oct 2007 01:48:42 -0000 Received: from unknown (96.226.25.79) by smtpout05-04.prod.mesa1.secureserver.net (64.202.165.221) with ESMTP; 08 Oct 2007 01:48:42 -0000 Message-ID: <47098C79.2030700@computer.org> Date: Sun, 07 Oct 2007 20:48:41 -0500 From: Eric Schuele User-Agent: Thunderbird 2.0.0.6 (X11/20070921) MIME-Version: 1.0 To: Tijl Coosemans References: <46FC8079.6030304@computer.org> <470961E4.8060700@computer.org> <200710080209.33529.tijl@ulyssis.org> In-Reply-To: <200710080209.33529.tijl@ulyssis.org> X-Enigmail-Version: 0.95.2 OpenPGP: url=http://www.ravenlock.us/files/pub_schuele.pgp Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4FE5809987C3780CC6E183D0" Cc: Kip Macy , freebsd-current@freebsd.org, Steve Kargl Subject: Re: Trouble with GDB and specific app on 7.0-CURRENT.... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2007 01:48:44 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4FE5809987C3780CC6E183D0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable On 10/07/2007 19:09, Tijl Coosemans wrote: > On Monday 08 October 2007 00:47:00 Eric Schuele wrote: >> On 10/07/2007 17:44, Kip Macy wrote: >>> On 9/27/07, Eric Schuele wrote: >>>> On 09/28/2007 00:12, Steve Kargl wrote: >>>>> On Thu, Sep 27, 2007 at 11:58:35PM -0500, Eric Schuele wrote: >>>>>> On 09/27/2007 23:29, Steve Kargl wrote: >>>>>>> On Thu, Sep 27, 2007 at 11:18:01PM -0500, Eric Schuele wrote: >>>>>>>> Has anyone seen behavior like this? What else can I provide >>>>>>>> that might help diagnose this? >>>>>>> Are you by any chance using tcsh as your shell? >>>>>> heh... Yes, as a matter of fact. How is that affecting me? I've >>>>>> always used tcsh and not had these troubles. >>>>> Signal handling in tcsh is broken, and one manifestation of >>>>> the problem is the behavior you're seeing with gdb. I've >>>>> repeatedly asked to have the 6.15.0 version of tcsh backed >>>>> out of src/ to the previously working 6.14.0 version, but no >>>>> one who can affect such a change seems to think a default user >>>>> shell with broken signal handling is a problem. The only >>>>> workaround that I've found is "setenv SHELL sh" prior to >>>>> executing gdb. >>>> Hmm... yeah.. I found the bug report after you mentioned tcsh. >>>> However changing that var has no effect for me. In fact using sh >>>> as my shell makes no difference either. >>>> >>>> Maybe I should rollback my tcsh and see what happens? >>> You need to actually execute a different shell. Changing the >>> variable isn't going to help. >> I did execute a different shell. Tried several in fact. >=20 > I'm not sure it will help, but you might want to give the patch in > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D115469 a try. >=20 >=20 To read the description, I don't believe I am experiencing this problem. After further investigation, I came to the following conclusion. Imagine one function, main() for example, written to call another function, my_func(), 10 times. However on the 6th call to said function... gdb refuses to step into the function... instead taking 100% of your cpu, seemingly forever. That is what I am seeing. Do you still think the patch is applicable to my situation? If so I will give it a shot. --=20 Regards, Eric --------------enig4FE5809987C3780CC6E183D0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHCYx5ngSDRM3IXUoRAjIiAKDAhfH5IKgujj2fOWwRO+bg+XAoEwCfbgU+ aSS7CORdrJGoBfogoMYtI4w= =ioMa -----END PGP SIGNATURE----- --------------enig4FE5809987C3780CC6E183D0--