From: Christo Crause <christo.crause@gmail.com>
To: "J.R. Heisey" <jrheisey@raytheon.com>
Cc: gdb@sourceware.org
Subject: Re: gdb usage help
Date: Fri, 15 Nov 2019 04:51:00 -0000 [thread overview]
Message-ID: <CAGOmfbFxQNWOokjNpx4W7-00oHiA_TAFQfgm1Zes4XgehOjmbA@mail.gmail.com> (raw)
In-Reply-To: <26ebd26c79bd4afc982a2374045cf829@DM2F00803MB0042.008f.mgd2.msft.net>
On Fri, 15 Nov 2019, 02:08 J.R. Heisey, <jrheisey@raytheon.com> wrote:
> Hi,
>
> I sometimes have issues and am looking for a place to ask questions. Is
> this the appropriate forum?
>
Yes, see mailing list description from
https://www.gnu.org/software/gdb/mailing-lists/:
A list for general discussion about GDB. Any GDB-related subject not
covered by another list is appropriate here; in practice, most of the
discussions are about ideas for future changes. Patches should be sent
to *gdb-patches
<https://www.gnu.org/software/gdb/mailing-lists/#gdb-patches>*. Bugs should
be reported using the Bug Database <https://www.gnu.org/software/gdb/bugs>.
>
prev parent reply other threads:[~2019-11-15 4:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 0:07 J.R. Heisey
2019-11-15 4:51 ` Christo Crause [this message]
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=CAGOmfbFxQNWOokjNpx4W7-00oHiA_TAFQfgm1Zes4XgehOjmbA@mail.gmail.com \
--to=christo.crause@gmail.com \
--cc=gdb@sourceware.org \
--cc=jrheisey@raytheon.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