On 10/9/14, 9:06 PM, jon wrote:
> On Thu, 2014-10-09 at 19:56 -0400, Chet Ramey wrote:
>> On 10/8/14, 8:17 PM, jon wrote:
>>> dmesg.....
>>>
>>> [307688.764489] configure[25847]: segfault at 9558104 ip 080e2246 sp
>>> bfd478f0 error 4 in bash[8048000+148000]
>>> [307689.436739] configure[25966]: segfault at 95580b4 ip 080e2246 sp
>>> bfd478f0 error 4 in bash[8048000+148000]
>>> [307689.467279] configure[25983]: segfault at 9558104 ip 080e2246 sp
>>> bfd478f0 error 4 in bash[8048000+148000]
>>>
>>> ./configure
>>
>> I can't reproduce this on Mac OS X or RHEL 5 using `bash ./configure' (so
>> I know what version of bash is running the script). Since configure starts
>> with `#! /bin/sh', it's going to run whatever version of bash you have
>> installed as /bin/sh.
>>
>> If you don't get the same results if you run `bash ./configure', open a
>> bug report with your vendor against /bin/sh.
>>
> I am the vendor, this is custom linux distro for DVR machines that I
> maintain.
>
>
> It gets even stranger.
Hmm...the leading !# /bin/sh makes ./configure turn into
/bin/sh ./configure
after the kernel gets done with it. Do you get the seg fault when running
that?
> I also tried
> bash -c './configure' that segfaults.
Sure, that does the same thing.
>
> I attached strace to the bash session running ./configure - it forks but
> I re-attached to the child to get this, not sure that helps though ...
What would really help is a stack traceback from gdb on the core dump from
the seg fault.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
