Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: Jonas Maebe <jonas.maebe@elis.ugent.be>,
	       GDB Development <gdb@sourceware.org>
Subject: Re: Fwd: [Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows
Date: Mon, 17 Feb 2014 08:01:00 -0000	[thread overview]
Message-ID: <20140217080033.GA26679@host2.jankratochvil.net> (raw)
In-Reply-To: <5301528A.2050302@gmail.com>

On Mon, 17 Feb 2014 01:06:34 +0100, asmwarrior wrote:
> On 2014-2-17 2:31, Jonas Maebe wrote:
> > Is this the right place to report bug tracker spam?
> I also received a lot of such spam emails recently.

There is rather #overseers at irc.freenode.net and there is also:
	https://sourceware.org/ml/overseers/


Jan


  parent reply	other threads:[~2014-02-17  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10004-3597-dF8jDtFSDR@http.sourceware.org/bugzilla/>
2014-02-16 18:31 ` Jonas Maebe
     [not found]   ` <5301528A.2050302@gmail.com>
2014-02-17  8:01     ` Jan Kratochvil [this message]
2014-02-17  8:04     ` Joel Brobecker

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=20140217080033.GA26679@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=asmwarrior@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=jonas.maebe@elis.ugent.be \
    /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