From: Greg Clayton <clayborg@gmail.com>
To: overseers@sourceware.org
Subject: I would like to file a bug on GDB
Date: Tue, 23 Aug 2022 14:46:08 -0700 [thread overview]
Message-ID: <50F37B53-4DF1-4EB8-AF42-6254427C8143@gmail.com> (raw)
Hello,
I am trying to create a bugzilla account so I can file a bug on GDB. I tried to create a new account online and saw the following message:
Because of spam user account creation has been restricted.
Contact your administrator or the maintainer (overseers@sourceware.org) for information about creating an account. Please mention the project you would like to create a bug for.
I work on LLVM, Clang and LLDB quite a bit as an open source contributor with the username of “clayborg” if you need to see my work. Here is a recent LLDB patch I have been working on:
https://reviews.llvm.org/D131437 <https://reviews.llvm.org/D131437>
I have a GDB bug I need to report with a possible fix that fixes an issue in the GDB DWARF parser.
Let me know how I can proceed,
Greg Clayton
clayborg@gmail.com
next reply other threads:[~2022-08-23 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 21:46 Greg Clayton [this message]
2022-08-23 21:56 ` Mark Wielaard
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=50F37B53-4DF1-4EB8-AF42-6254427C8143@gmail.com \
--to=clayborg@gmail.com \
--cc=overseers@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).