From: Andrew Cagney <ac131313@redhat.com>
To: glenn_engel@agilent.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: patch to gdbserver for names instead of pid numbers
Date: Tue, 10 Dec 2002 12:01:00 -0000 [thread overview]
Message-ID: <3DF646FF.1020708@redhat.com> (raw)
In-Reply-To: <FC0B9DA2600ED4118F76009027AA5DDD06B3F103@ALEX2>
>> No... you can do this using 'gdbserver :1234 --attach `pidof -s foo`.
>> Killall5/pidof is a 9K binary; I don't want to add this feature to the
>> server directly when it's already available so lightweightly.
>
>
> Excellent ! Someday I'll know every command available and then I'll die happy... Thanks.
Hmm, can you create a bug report describing this (see
http://sources.redhat.com/gdb/bugs/) (or better update the documentation
:-)? It should be mentioned in the documentation.
Andrew
next prev parent reply other threads:[~2002-12-10 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 11:40 glenn_engel
2002-12-10 12:01 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-09 14:33 glenn_engel
2002-12-10 11:37 ` 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=3DF646FF.1020708@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=glenn_engel@agilent.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