From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: examining remote core dumps; MT support for attach;
Date: Fri, 13 Jun 2003 15:48:00 -0000 [thread overview]
Message-ID: <3EE9F153.50605@redhat.com> (raw)
In-Reply-To: <20030613133905.GD29641@nevyn.them.org>
> On Fri, Jun 13, 2003 at 09:31:23AM -0400, Andrew Cagney wrote:
>
>> >On Thu, Jun 12, 2003 at 05:17:03PM -0400, nak26 wrote:
>> >
>
>> >>>> How hard would it be to add support for that? I can give it a try, but
>
>> >
>
>> >>would
>
>> >
>
>> >>>> need some guidance...
>
>> >
>
>> >>>
>> >>>I have no idea how you would do it. You'd have to transfer essentially
>> >>>the same info anyway. Or port gdbserver to have a "core file" target
>> >>>but I don't know how well that would work.
>
>> >
>
>> >>
>> >>What do you mean by "Or port gdbserver to have a "core file" target
>> >>but I don't know how well that would work"?
>
>> >
>> >
>> >Allow gdbserver to read from a core file instead of a running process.
>> >It would be tricky; you'll have to figure out how to do it yourself.
>
>>
>> There was a suggestion made that GDB could manipulate files on the
>> remote system (mainly to get at /proc/auxv). Such a mechanism would
>> also address the core file problem.
>
>
> This is a reasonable idea, but I think our current remote protocol is
> not quite up to the task. Let's keep it on the list along with
> multiple channels (for I/O) and file upload/download...
qPread;FILE,OFFSET,LENGTH
qPwrite:FILE,OFFSET,DATA
Andrew
next prev parent reply other threads:[~2003-06-13 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 21:17 nak26
2003-06-13 13:19 ` Daniel Jacobowitz
2003-06-13 13:31 ` Andrew Cagney
2003-06-13 13:39 ` Daniel Jacobowitz
2003-06-13 15:48 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-13 14:18 nak26
2003-06-12 21:02 nak26
2003-06-12 21:01 nak26
2003-06-12 21:08 ` Daniel Jacobowitz
2003-06-12 20:18 nak26
2003-06-12 20:41 ` Kevin Buettner
2003-06-12 20:03 nak26
2003-06-12 20:11 ` Daniel Jacobowitz
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=3EE9F153.50605@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.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).