Hi. Thanks for the attention. Here's a backtrace: summon. : disown. read. *** glibc detected *** /bin/bash: double free or corruption (fasttop): 0x00000000006caa60 ***
Program received signal SIGSEGV, Segmentation fault. 0x00007ffff740c685 in ?? () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff740c685 in ?? () from /lib64/libc.so.6 #1 0x00007ffff740e2c4 in ?? () from /lib64/libc.so.6 #2 0x00007ffff7412298 in calloc () from /lib64/libc.so.6 #3 0x00007ffff7de5a6f in ?? () from /lib64/ld-linux-x86-64.so.2 #4 0x00007ffff7de10e6 in ?? () from /lib64/ld-linux-x86-64.so.2 #5 0x00007ffff7de2f06 in ?? () from /lib64/ld-linux-x86-64.so.2 #6 0x00007ffff7ded799 in ?? () from /lib64/ld-linux-x86-64.so.2 #7 0x00007ffff7de92a6 in ?? () from /lib64/ld-linux-x86-64.so.2 #8 0x00007ffff7ded23a in ?? () from /lib64/ld-linux-x86-64.so.2 #9 0x00007ffff74b3af2 in ?? () from /lib64/libc.so.6 #10 0x00007ffff7de92a6 in ?? () from /lib64/ld-linux-x86-64.so.2 #11 0x00007ffff74b3b8f in ?? () from /lib64/libc.so.6 #12 0x00007ffff74b3c01 in __libc_dlopen_mode () from /lib64/libc.so.6 #13 0x00007ffff748e925 in ?? () from /lib64/libc.so.6 #14 0x00007ffff748ea6d in backtrace () from /lib64/libc.so.6 #15 0x00007ffff7406e77 in ?? () from /lib64/libc.so.6 #16 0x00007ffff740c375 in ?? () from /lib64/libc.so.6 #17 0x0000000000471aac in read_builtin () #18 0x000000000042ba92 in ?? () #19 0x000000000042f32c in execute_command_internal () #20 0x000000000043167a in ?? () #21 0x000000000042d214 in execute_command_internal () #22 0x0000000000430ede in execute_command () #23 0x00000000004312f5 in ?? () #24 0x000000000042d233 in execute_command_internal () #25 0x0000000000430ede in execute_command () #26 0x000000000041ba31 in reader_loop () #27 0x000000000041add5 in main () On Fri, Jan 25, 2013 at 12:28 AM, Chet Ramey <chet.ra...@case.edu> wrote: > On 1/24/13 8:35 AM, konsolebox wrote: > > Hi. Is there a way to prevent this segmentation fault in Bash? I'm not > sure > > where the fault happens but when there's a function that handles a trap > and > > when a signal is caught during a session of read with -t, Bash crashes. > An > > example code that makes this happen is this: > > I ran this script through around 6000 cycles on RHEL 5 using bash-4.2.42, > built with and without the bash malloc, and didn't see a crash. > > How about a stack traceback from one of the crashes you get? > > 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/ >
