Date: Sun, 13 May 2007 20:56:37 -0700 From: Mark Peek <mp@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: Process for requesting reverting patch? Message-ID: <4647DDF5.6070400@FreeBSD.org> In-Reply-To: <20070514031852.GA634@troutmask.apl.washington.edu> References: <864pmg1t1s.fsf@dwp.des.no> <20070513183009.GA96018@troutmask.apl.washington.edu> <86646wzfv0.fsf@dwp.des.no> <20070513192836.GA94258@troutmask.apl.washington.edu> <46478626.9060301@FreeBSD.org> <20070513225255.GA96773@troutmask.apl.washington.edu> <20070513230634.GA96931@troutmask.apl.washington.edu> <6eb82e0705131931j4274046ew588ba5f28c0930e2@mail.gmail.com> <20070514025129.GB197@troutmask.apl.washington.edu> <6eb82e0705132011r6bad8de6qb38eb6e6bcb4beb0@mail.gmail.com> <20070514031852.GA634@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/13/07 8:18 PM, Steve Kargl wrote: > For any one that thinks I'm some kind of idiot. I've > used the base system gdb for the past 3 years to debug > gcc. It worked flawlessly until the recent tcsh import. I was able to reproduce a gdb hang after receiving the additional information about the "setenv MAIL /var/log/`whoami`" in the .cshrc file. I believe it might be due to some changes in signal handling between tcsh 6.14 and 6.15. I'll try debugging it further myself and I also notified the tcsh bug list about this issue in case someone on that list can help as well. Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4647DDF5.6070400>