From: Torbjorn SVENSSON <torbjorn.svensson@st.com>
To: Mark Wielaard <mark@klomp.org>,
Overseers mailing list <overseers@sourceware.org>
Subject: RE: Problem reporting error on bugzilla and account blocked
Date: Tue, 30 Aug 2022 08:25:28 +0000 [thread overview]
Message-ID: <AM6PR10MB2197BC59319CCAB65F8E774F81799@AM6PR10MB2197.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <Yw0scT64pkHZVgNM@wildebeest.org>
Hello,
Thanks for the fast reply.
I was able to create the Bugzilla entry (https://sourceware.org/bugzilla/show_bug.cgi?id=29538) after moving the output from GDB with the RSP to an attachment.
Kind regards,
Torbjörn
> -----Original Message-----
> From: Mark Wielaard <mark@klomp.org>
> Sent: den 29 augusti 2022 23:15
> To: Overseers mailing list <overseers@sourceware.org>
> Cc: Torbjorn SVENSSON <torbjorn.svensson@st.com>
> Subject: Re: Problem reporting error on bugzilla and account blocked
>
> Hi Tobjorn,
>
> On Mon, Aug 29, 2022 at 07:21:59PM +0000, Torbjorn SVENSSON via Overseers
> wrote:
>
> > I was on IRC chatting with "simark" about and issue with remote
> > debugging and how the "target remote"-sequence was handled in GDB.
> > To investigate the issue further, simark asked me to create a
> > Bugzilla, but Bugzilla reported that my report had "inappropriate
> > content". I have no idea what the inappropriate content is, but I've
> > included it in the mail below.
> >
> > Please let me know what I should change in order for the bug report to be
> accepted.
>
> I think the gdb remote protocol dump looks like spam to bugzilla.
> I suggest putting the command file and gdb output in separate attachments.
>
> > If you are unsure, yes, I am a human and have contributed to GDB in the
> past.
> > Please also restore my account.
>
> Restored! Sorry for the inconvenience.
>
> Cheers,
>
> Mark
prev parent reply other threads:[~2022-08-30 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 19:21 Torbjorn SVENSSON
2022-08-29 21:15 ` Mark Wielaard
2022-08-30 8:25 ` Torbjorn SVENSSON [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=AM6PR10MB2197BC59319CCAB65F8E774F81799@AM6PR10MB2197.EURPRD10.PROD.OUTLOOK.COM \
--to=torbjorn.svensson@st.com \
--cc=mark@klomp.org \
--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).