This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug backtrace/20746] hit assert, when 'thread apply all bt'.
- From: "v at tenable dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 29 Oct 2016 14:14:11 +0000
- Subject: [Bug backtrace/20746] hit assert, when 'thread apply all bt'.
- Auto-submitted: auto-generated
- References: <bug-20746-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20746
v at tenable dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|hit assert, when 'thread |hit assert, when 'thread
|apply all bt' in |apply all bt'.
|noninteractive mode. |
--- Comment #1 from v at tenable dot com ---
========================
=== symptom, addit'l ===
Same thing happens in interactive mode, after attaching to already-running
process!
(gdb) set breakpoint pending off
(gdb) set print address off
(gdb) set print pretty off
(gdb) set print vtbl off
(gdb) py gdb.pretty_printers=[]
(gdb) thread apply all bt
Thread 47 (Thread 0x7f3c43402700 (LWP 119404)):
#0 pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1 lce__condvar_timedwait (stack.c:613: internal-error: print_frame_args:
Assertion `nsym != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n
This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.
stack.c:613: internal-error: print_frame_args: Assertion `nsym != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.
(gdb)
--
You are receiving this mail because:
You are on the CC list for the bug.