From: Andrew Cagney <ac131313@redhat.com>
To: Roland McGrath <roland@redhat.com>, Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb support for Linux vsyscall DSO
Date: Mon, 12 May 2003 19:23:00 -0000 [thread overview]
Message-ID: <3EBFF332.7040108@redhat.com> (raw)
In-Reply-To: <3EBD73CA.10807@redhat.com>
> Any way, re-reading your post yes, the info is in there. If the address is known, GDB can pull the contents out of memory. Given the list of targets:
>
> - core
> - native attach
> - native run
> - remote
> - ?more?
>
> I believe the choices are:
>
> - find a way of determing that address across all of these targets :-/
> - implement per-target custom mechanisms for pulling out this information (creating a need to test/implement each target separatly - vis the corefile + dwarf2 changes) :-//
>
> So, it possible to find the address (symbol?, /proc, shlib load table, ...?) for all targets?
>
> /proc/PID/map, on a remote, is a possability. A remote version of find_memory_regions() would be useful anyway - clean up gcore a bit. However, the down side is that a system with no /proc mounted wouldn't debug very well :-/
To follow up my own e-mail. On Solaris, there is:
/proc/PID/auxv
and the corresponding core file includes a .note section that contains
(man core.4):
auxv_t array
n_type: NT_AUXV. This entry contains the array of
auxv_t structures that was passed by the operating
system as startup information to the dynamic linker.
Auxiliary vector information is defined in
<sys/auxv.h>.
So the /proc solution even as ``prior art''.
As for the remote case, I think GDB's remote protocol (via the target
vector) should allow access to the remote file system (lib*.so, /proc,
....) anyway. Doing that would let the OS dependant code access the
remote /proc/PID/aux. All sorts of useful things would suddenly ``just
work''.
To me this looks like the simplest and cleanest way of solving the
problem. A conistent mechanism to find the address, and a single
technique for accessing the .eh_frame info. That has to be better than
approaches that require per-target custom modifications for what is a
Linux specific problem.
Andrew
next prev parent reply other threads:[~2003-05-12 19:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 9:45 gdb/dwarf-frame.c Roland McGrath
2003-05-09 13:41 ` gdb/dwarf-frame.c Daniel Jacobowitz
2003-05-09 14:10 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-09 14:56 ` NPTL thread support H. J. Lu
2003-05-09 15:44 ` Elena Zannoni
[not found] ` <20030509091522.A2960@lucon.org>
[not found] ` <16059.55278.841645.134311@localhost.redhat.com>
2003-05-11 20:46 ` H. J. Lu
2003-05-12 19:24 ` J. Johnston
2003-05-12 20:08 ` H. J. Lu
2003-05-12 20:15 ` David Carlton
2003-05-12 21:09 ` Andrew Cagney
2003-05-12 21:18 ` David Carlton
2003-05-12 21:23 ` Daniel Jacobowitz
2003-05-12 20:17 ` Elena Zannoni
2003-05-09 17:01 ` gdb/dwarf-frame.c Andrew Cagney
2003-05-09 17:08 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-09 19:43 ` gdb/dwarf-frame.c Mark Kettenis
2003-05-09 21:19 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 21:48 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-09 22:17 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 21:54 ` gdb/dwarf-frame.c Andrew Cagney
2003-05-09 21:58 ` gdb/dwarf-frame.c Daniel Jacobowitz
2003-05-09 22:18 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 22:28 ` gdb/dwarf-frame.c Andrew Cagney
2003-05-09 22:33 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 20:32 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 19:36 ` gdb/dwarf-frame.c Mark Kettenis
2003-05-09 21:34 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 21:46 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-10 7:07 ` gdb support for Linux vsyscall DSO Roland McGrath
2003-05-10 17:24 ` Andrew Cagney
2003-05-10 18:13 ` Daniel Jacobowitz
2003-05-10 19:42 ` Roland McGrath
2003-05-10 21:49 ` Andrew Cagney
2003-05-12 19:23 ` Andrew Cagney [this message]
2003-05-13 2:29 ` Roland McGrath
2003-05-13 16:03 ` Andrew Cagney
2003-05-10 21:28 ` Roland McGrath
2003-05-10 17:55 ` Mark Kettenis
2003-05-10 20:27 ` Roland McGrath
2003-05-11 23:14 ` Mark Kettenis
2003-05-13 1:53 ` Roland McGrath
2003-05-15 21:26 ` Mark Kettenis
2003-05-16 2:25 ` Roland McGrath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EBFF332.7040108@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=roland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).