From: Jim Elgin <elgin@shore.net>
To: gdb-patches@cygnus.com
Subject: Re: Some questions about GNU GDB (fwd)
Date: Fri, 26 Mar 1999 09:59:00 -0000 [thread overview]
Message-ID: <199903261759.MAA17360@claudia.elgin.net> (raw)
Message-ID: <19990326095900.NmOoRuQkjDn66VvAaKPa5Cl0YRLZVXXE9wD8bcQy-7A@z> (raw)
In-Reply-To: <199903261723.MAA16775@claudia.elgin.net>
Hi
I am forwarding a request for help that we received at gvc@gnu.org. This
person does not state at all clearly that they are offering to help you,
but I will let you decide if you wish to follow up.
Jim
Forwarded message:
> From gnulists@mescaline.gnu.org Thu Mar 25 18:03:48 1999
> Resent-From: Project GNU <gnu@gnu.org>
> Resent-Message-Id: <199903252251.RAA27782@delysid.gnu.org>
> Message-Id: <199903252251.RAA27782@delysid.gnu.org>
> Resent-Date: 25 Mar 1999 17:51:28 -0500
> Resent-To: gvc@gnu.org
> Date: Thu, 25 Mar 1999 12:42:47 +0100 (MET)
> From: Magdalena Sujecka <maggee@ask.eti.pg.gda.pl>
> X-Sender: maggee@nico14.eti.pg.gda.pl
> To: gnu@gnu.org
> Subject: Some questions about GNU GDB
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> X-UIDL: e1e9fd05fc064d9e4de4269eee4d9caf
>
> Hello,
>
> I am much interested in remote debugging with GDB. I know that I have to
> write a stub, but I don't know how to manage it. I have read the
> Stallman's guide - it is not sufficient for implementation. I need this
> stubs for SPARC and for PC.
>
> I would be obliged for any help....
>
> Thank you
>
> >>>>> Magda Sujecka <<<<< Festina lente ! >>>>>
>
>
>
>
>
>
>
--
Jim Elgin
Gnu Volunteer Coordinator
elgin@gnu.org
next parent reply other threads:[~1999-03-26 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199903261723.MAA16775@claudia.elgin.net>
1999-04-01 0:00 ` Jim Elgin [this message]
1999-03-26 9:59 ` Jim Elgin
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=199903261759.MAA17360@claudia.elgin.net \
--to=elgin@shore.net \
--cc=gdb-patches@cygnus.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