Description Sergey Prigogin 2013-08-20 13:50:09 EDT

The following GDB trace shows a stopped notification *after* Eclipse has tried to set a breakpoint. Setting the breakpoint failed because the thread was still running.

605,309 64-exec-interrupt --thread 86
605,309 64^done
605,310 (gdb)
605,311 65-break-insert --thread-group i1 -f myclass.cc:112
605,404 65^error,msg="Cannot access memory at address 0x1aee158"
605,404 =thread-selected,id="1"
605,404 (gdb)
605,405 66-exec-continue --thread 86
605,405 66^error,msg="Cannot execute this command while the selected thread is running."
605,405 (gdb)
605,406 67-exec-continue --thread 86
605,406 67^error,msg="Cannot execute this command while the selected thread is running."
605,406 (gdb)
792,738 *stopped,reason="signal-received",signal-name="SIGINT",signal-meaning="Interrupt",frame={add\
r="0x00007f8093ff8a93",func="epoll_wait",args=[],from="/usr/grte/v3/lib64/libc.so.6"},thread-id="1",\
stopped-threads=["1"],core="8"