bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bashdb sig-test.sh failure


From: Rocky Bernstein
Subject: bashdb sig-test.sh failure
Date: Mon, 26 Oct 2015 13:25:08 -0400

Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H   -I.  -I../. -I.././include -I.././lib  -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall
uname output: Linux muffin 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu

Bash Version: 4.3
Patch Level: 11
Release Status: release

Description:
        
Weird trap debug and signal handling problem in bashdb in running test test/integration/test-sig..sh. I've tried to narrow to scope of the problem by reducing the debugger commands that are invoked as well as the script that gets debugged. Attempts to write a small standalone program though elude me.  

Gdb show that bash is attempting to free memory from discard_pipeline() inside a restore_pipeline() which is in running run_debug_trap(). See the attached gdb backtrace.
See also https://sourceforge.net/p/bashdb/bugs/36/ https://sourceforge.net/p/bashdb/bugs/37/ for  where this was first reported. 

Repeat-By:

Save attached sig-bug.cmd-ok and sig-bug.sh files and then run: 

bashdb -q --no-init -x sig-bug.cmd-ok sig-bug.sh


Attachment: sig-bug.cmd-ok
Description: Binary data

Attachment: sig-bug.sh
Description: Bourne shell script

Attachment: gdb-session.log
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]