From: Daniel Jacobowitz <drow@mvista.com>
To: nak26 <nak26@drexel.edu>
Cc: drow <drow@montavista.com>, gdb <gdb@sources.redhat.com>
Subject: Re: examining remote core dumps; MT support for attach;
Date: Thu, 12 Jun 2003 21:08:00 -0000 [thread overview]
Message-ID: <20030612210831.GA16404@nevyn.them.org> (raw)
In-Reply-To: <3EE917EC@webmail.drexel.edu>
On Thu, Jun 12, 2003 at 04:59:55PM -0400, nak26 wrote:
> >>> 1. Is it possible to examine a core file on a remote machine, in the
> cases,
> >> where fetching the core is undesirable due to the thinness of the pipe.
> >
> >This is not supported.
>
> 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.
> >> 2. Does the gdbserver that comes with gdb5.3 work with multithreaded apps,
> or
> >> it needs to be additionally patched?
> >
> >It should work.
>
> I saw a PREPARE_TO_PROCEED patch beeing mentioned in some of the posts. In
> which cases it heeds to be applied?
You'll probably never hit it unless you manually use the "thread"
command to switch threads and then single-step the new thread.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-12 21:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 21:01 nak26
2003-06-12 21:08 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-13 14:18 nak26
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
2003-06-12 21:02 nak26
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=20030612210831.GA16404@nevyn.them.org \
--to=drow@mvista.com \
--cc=drow@montavista.com \
--cc=gdb@sources.redhat.com \
--cc=nak26@drexel.edu \
/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).