This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/12074] multi-inferior internal error
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 11 Apr 2012 15:02:34 +0000
- Subject: [Bug threads/12074] multi-inferior internal error
- Auto-submitted: auto-generated
- References: <bug-12074-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12074
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #2 from Pedro Alves <palves at redhat dot com> 2012-04-11 15:02:34 UTC ---
#1 - GDB doesn't support having multiple target stack active, so you can only
debug multiple inferiors if they're all controlled by the same target.
#2 - The core target (corelow.c, mostly) doesn't support debugging multiple
cores. E.g., core_bfd is a global.
The original report is about issuing "run" while debugging a core, which due to
the above would break. As an intermediate step, GDB now pops the current
target from the stack, along with getting rid of all its inferiors, when you
switch to a ptrace-based target (IOW, core -> process). Not ideal, but better
than breaking down.
> (gdb) inferior 2
> [Switching to inferior 2 [<null>] (<noexec>)]
> (gdb) file sleep
> warning: core file may not match specified executable file.
Caused by the points above, mostly by #2 (core_bfd global).
--
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.