From: Dmitry Samersoff <dms@samersoff.net>
To: Fei Ding <fdingiit@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: How to add a new command?
Date: Thu, 26 Mar 2015 07:55:00 -0000 [thread overview]
Message-ID: <5513BB82.6010900@samersoff.net> (raw)
In-Reply-To: <CAGmPkf+_LZdUpz=jcXGNBbaqpJqzmZfkeF5qKxJZTwX9omi8-Q@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Fei,
Take a look at the Abhijith's patch:
https://sourceware.org/ml/gdb-patches/2012-05/msg00500.html
- -Dmitry
On 2015-03-26 05:59, Fei Ding wrote:
> Hi all:
>
> I want to add a new command to GDB based on my team's requirement,
> like `(gdb) auto-check [input file]` , but I found it a litter bit
> difficult to find related source code. I guess GDB should
> initialize all command at some place, and I plan to learn from it
> first. Any body familiar with this? I just need some files' names
> of source code ,maybe function names is even more useful.
>
> Thanks.
>
- --
Dmitry Samersoff
Saint Petersburg, Russia, http://devnull.samersoff.net
* There will come soft rains ...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJVE7uCAAoJEHEy08c4gIABvdsH/3DiAk9OYijIbbsumRDcEGbH
jZk4t/g1HiaxHyFMq9XaL11ZUazNMOV+k8inpQrijtW1nE8Rt/ogje0dYfFANSKB
mBAsbdXk7BGGEV6WLU2sxIZD+eFaaub5/cam9kmLAZSH8SvSzx07+4jkyex9z1t+
BXM+wxgkRx3Gpj35v6FzCYGsrztzy5XIGut8x1xp/RL/+guxnd01RMzEms2j+SFU
ScdP+SaRTvUwUkgqBCN3VJI6iyCyW/at9HJulLaEw4EhkWU31KBdBEogBWulGUQB
ht0XF1s4bOb80tuoc/4hzOF7tNwIEpZrEDtZGAhiqA2zBOATufcg9yNF9CO8mi8=
=YhE2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-03-26 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 2:59 Fei Ding
2015-03-26 3:49 ` Eli Zaretskii
2015-03-26 7:55 ` Dmitry Samersoff [this message]
2015-03-26 18:32 ` Doug Evans
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=5513BB82.6010900@samersoff.net \
--to=dms@samersoff.net \
--cc=fdingiit@gmail.com \
--cc=gdb@sourceware.org \
/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).