This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/23039] 'info program' always cause GDB aborts at early start
- From: "weimin.pan at oracle dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 15 Nov 2018 23:09:25 +0000
- Subject: [Bug gdb/23039] 'info program' always cause GDB aborts at early start
- Auto-submitted: auto-generated
- References: <bug-23039-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23039
weimin.pan at oracle dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |weimin.pan at oracle dot com
--- Comment #1 from weimin.pan at oracle dot com ---
The crash could easily be reproduced. Setting breakpoint at 0 causes
insert_breakpoint_locations to fail and find_thread_ptid to return a
NULL thread_info pointer in info_program_command. Dereferencing the
NULL pointer then triggers the crash.
Checking the return value from the find_thread_ptid call before
dereferencing it is one way to fix the problem.
--
You are receiving this mail because:
You are on the CC list for the bug.