This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] gdb could leave inferior running as a background process
On Tue, Apr 22, 2008 at 12:55 PM, Daniel Jacobowitz <drow@false.org> wrote:
> > > Where is the warning issued?
> >
> > #0 warning (string=0x82e9520 "(Internal error: pc 0x%s in read in
> > psymtab, but not in symtab.)\n") at
> > ../../../google_vendor_src_branch/gdb/gdb-6.8.x/gdb/utils.c:615
> > #1 0x08112c5b in find_pc_sect_symtab (pc=134512896, section=0x0) at
> > ../../../google_vendor_src_branch/gdb/gdb-6.8.x/gdb/symtab.c:1984
> > #2 0x08112d79 in find_pc_sect_line (pc=134512896, section=0x0,
> > notcurrent=0) at
> > ../../../google_vendor_src_branch/gdb/gdb-6.8.x/gdb/symtab.c:2140
> > #3 0x08112fcc in find_pc_line (pc=134512896, notcurrent=0) at
> > ../../../google_vendor_src_branch/gdb/gdb-6.8.x/gdb/symtab.c:2262
> > #4 0x08128698 in init_execution_control_state (ecs=0xffffd05c) at
> > ../../../google_vendor_src_branch/gdb/gdb-6.8.x/gdb/infrun.c:1128
> > #5 0x08128344 in wait_for_inferior (treat_exec_as_sigtrap=0) at
> > ../../../google_vendor_src_branch/gdb/gdb-6.8.x/gdb/infrun.c:1012
>
> Ugh. Perhaps we can do this before resuming.
It seems like there are multiple places where this can happen. E.g.
wait_for_inferior -> handle_inferior_event -> find_pc_partial_function
-> target_terminal_ours_for_output.