Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Apr 2005 14:24:38 -0400 (EDT)
From:      "Mike Jakubik" <mikej@rogers.com>
To:        "Frank Laszlo" <laszlof@tvog.net>
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: Reproducible sig 11 with bash2
Message-ID:  <4106.172.16.0.199.1112898278.squirrel@172.16.0.1>
In-Reply-To: <42553ED0.70707@tvog.net>
References:  <1724.172.16.0.199.1112814116.squirrel@wettoast.dyndns.org>    <20050406191652.GA26737@xor.obsecurity.org>    <1805.172.16.0.199.1112815734.squirrel@wettoast.dyndns.org>    <20050406193254.GA26965@xor.obsecurity.org> <1890.172.16.0.199.1112818160.squirrel@wettoast.dyndns.org> <42553ED0.70707@tvog.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, April 7, 2005 10:08 am, Frank Laszlo said:

> Trying compiling this against ports/devel/readline and see if it still
> exists. I've seen this bug before, I believe it has to do with bash's
> autocompletion. Give the readline port a shot

FYI. Bash v3 does not have this problem.

> At 5:56 PM -0400 4/6/05, Mike Jakubik wrote:
>
>> On Wed, April 6, 2005 6:45 pm, Garance A Drosihn said:
>>
>>>
>>> See:
>>> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/75315
>>>
>>>
>>> The PR includes instructions on a quick way around the problem, if
>>> it's something that you personally trip over very often (which I did,
>>> because I like typing in ...
>>
>> As i mentioned in my last email, recompiling system libreadline
>> with -O instead of default -O2 fixes the problem for me.
>
> I realize that, but I am pretty sure it is still true that the
> real problem is a mismatch in libreadline versions.  Changing the
> compile-time options may happen to solve the sig-11, but it might also
> leave some other obscure problems lurking around...
>
> The fix I did was the one in the PR, which was:
>
>
> cp /usr/include/readline/history.h ./work/bash-2.05b/lib/readline/
>
> I did not have to recompile the system libreadline at all.

Ok, thanks for the info! I will try your fix instead. I wonder how this
can be solved permanently though. Also, bash3 is out, would be intresting
to see if it too has this problem.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4106.172.16.0.199.1112898278.squirrel>