[Bug gdb/17247] New: gdb freezes on multi threaded app (test-case attached)

["glibc at iamsergio dot de" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17247

            Bug ID: 17247
           Summary: gdb freezes on multi threaded app (test-case attached)
           Product: gdb
           Version: 7.7
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: glibc at iamsergio dot de

Created attachment 7741
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7741&action=edit
test-case

Run the attached test-case:

g++ -std=c++11 -lpthread test.cpp -o test
gdb ./test
^C^C^C -> nothing, it's impossible to interrupt


Attaching a second gdb to the first gdb I can get a backtrace:

Thread 1 (Thread 0x7fbe58d58740 (LWP 3540)):
#0  0x00007fbe56c61157 in sigsuspend () from /usr/lib/libc.so.6
#1  0x00000000004a9270 in wait_lwp (lp=lp@entry=0x1edcee0) at linux-nat.c:2314
---Type <return> to continue, or q <return> to quit---
#2  0x00000000004a951e in wait_lwp (lp=lp@entry=0x1edcee0) at linux-nat.c:2370
#3  0x00000000004aad1c in stop_wait_callback (lp=0x1edcee0, data=<optimized
out>) at linux-nat.c:2591
#4  0x00000000004a9df9 in iterate_over_lwps (filter=...,
callback=callback@entry=0x4aacd0 <stop_wait_callback>, data=data@entry=0x0) at
linux-nat.c:1041
#5  0x00000000004ac414 in linux_nat_wait_1 (ops=<optimized out>,
target_options=1, ourstatus=0x7fffc63c4160, ptid=...) at linux-nat.c:3530
#6  linux_nat_wait (ops=<optimized out>, ptid=..., ourstatus=0x7fffc63c4160,
target_options=1) at linux-nat.c:3680
#7  0x00000000004b2676 in thread_db_wait (ops=<optimized out>, ptid=...,
ourstatus=0x7fffc63c4160, options=1) at linux-thread-db.c:1489
#8  0x00000000005e7c3d in delegate_wait (self=<optimized out>, arg1=...,
arg2=<optimized out>, arg3=<optimized out>) at target-delegates.c:116
#9  0x00000000005f5134 in target_wait (ptid=...,
status=status@entry=0x7fffc63c4160, options=options@entry=1) at target.c:2073
#10 0x00000000005b96e9 in fetch_inferior_event
(client_data=client_data@entry=0x0) at infrun.c:2881
#11 0x00000000005cf452 in inferior_event_handler (event_type=INF_REG_EVENT,
client_data=0x0) at inf-loop.c:58
#12 0x00000000005cd671 in process_event () at event-loop.c:340
#13 0x00000000005cda3a in gdb_do_one_event () at event-loop.c:392
#14 0x00000000005cdc8e in start_event_loop () at event-loop.c:429
#15 0x00000000005c7463 in captured_command_loop (data=data@entry=0x0) at
main.c:322
#16 0x00000000005c46aa in catch_errors (func=func@entry=0x5c7450
<captured_command_loop>, func_args=func_args@entry=0x0,
errstring=errstring@entry=0x7990d2 "", mask=mask@entry=RETURN_MASK_ALL) at
exceptions.c:514
#17 0x00000000005c83d6 in captured_main (data=data@entry=0x7fffc63c4450) at
main.c:1178
#18 0x00000000005c46aa in catch_errors (func=func@entry=0x5c7960
<captured_main>, func_args=func_args@entry=0x7fffc63c4450,
errstring=errstring@entry=0x7990d2 "", mask=mask@entry=RETURN_MASK_ALL)
    at exceptions.c:514
#19 0x00000000005c88ab in gdb_main (args=args@entry=0x7fffc63c4450) at
main.c:1186
#20 0x0000000000464dc5 in main (argc=<optimized out>, argv=<optimized out>) at
gdb.c:32

Tested gdb 7.7 and master, on archlinux, kernel 3.14.15, glibc 2.19, gcc 4.9.1,
also tested clang, same bug.

Using x86_64

-- 
You are receiving this mail because:
You are on the CC list for the bug.