Date: Fri, 13 Apr 2007 22:22:57 -0700 From: Julian Elischer <julian@elischer.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: gdb is broken Message-ID: <46206531.2050405@elischer.org> In-Reply-To: <20070414051628.GA40509@troutmask.apl.washington.edu> References: <20070413183525.GA34643@troutmask.apl.washington.edu> <20070413221843.GA37592@troutmask.apl.washington.edu> <20070414002044.GA38494@troutmask.apl.washington.edu> <20070414051628.GA40509@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote:
> On Fri, Apr 13, 2007 at 05:20:44PM -0700, Steve Kargl wrote:
>> On Fri, Apr 13, 2007 at 03:18:43PM -0700, Steve Kargl wrote:
>>> On Fri, Apr 13, 2007 at 11:35:25AM -0700, Steve Kargl wrote:
>>>> It appears that someone has broken gdb in -current.
>>>>
>>>> laptop:kargl[250] cat > hello.c
>>>> #include <stdio.h>
>>>> int main(void) {
>>>> printf("Hello world!\n");
>>>> return 0;
>>>> }
>>>> laptop:kargl[251] cc -o z -g hello.c
>>>> laptop:kargl[252] ./z
>>>> Hello world!
>>>> laptop:kargl[253] gdb z
>>>> (gdb) run
>>>> Starting program: /usr/home/kargl/tmp/z
>>>> Terminated
>>>>
>>>> gdb appears to spwan the csh comamnd below and then just spins.
>>>>
>>> Reverting to a March 01, 2007 -current gives
>>>
>>> (gdb) run
>>> Starting program: /usr/home/kargl/tmp/z
>>> Hello world!
>>>
>>> Program exited normally.
>>>
>>> the expected result. A binary search for the guilty commit
>>> is going to be a PITA on my old laptop.
>> A March 31, 2007 -current exibits a broken gdb. Up next
>> March 15, 2007.
>>
>
> I've narrowed the problem down to the 22-26 Mar 07 range.
>
there was a new version of csh in that period.. (or close to it...)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46206531.2050405>