This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/13463] New: bad multi-inferior behavior withbreakpoint resetting
- From: "tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 01 Dec 2011 18:49:43 +0000
- Subject: [Bug breakpoints/13463] New: bad multi-inferior behavior withbreakpoint resetting
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13463
Bug #: 13463
Summary: bad multi-inferior behavior with breakpoint resetting
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
AssignedTo: unassigned@sourceware.org
ReportedBy: tromey@redhat.com
Classification: Unclassified
I tried to use gdb to debug gdb in a multi-inferior case,
by running the test suite. To reproduce:
* cd $build/gdb/testsuite
* gdb /usr/bin/make
* Set up for multi-inferior. I use at least:
set detach-on-fork off
set schedule-multiple on
set pagination off
set target-async on
set non-stop on
set print inferior-events on
* add-inferior -exec ../gdb
* inferior 2
* b internal_error
* run check RUNTESTFLAGS=py-mi.exp
Now a couple of strange things happen.
First, I see some warnings like this:
process 15935 is executing new program: /usr/bin/iconv
Error in re-setting breakpoint 1: Cannot access memory at address 0x494f22
Error in re-setting breakpoint 1: Cannot access memory at address 0x494f22
Error in re-setting breakpoint 1: Cannot access memory at address 0x494f22
Error in re-setting breakpoint 1: Cannot access memory at address 0x494f22
[Inferior 33 (process 15935) exited normally]
Second, I get this sometimes:
Cannot find new threads: capability not available
(This error would be improved by printing the inferior information)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.