From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: GDB Development <gdb@sourceware.org>
Subject: Fwd: [Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows
Date: Sun, 16 Feb 2014 18:31:00 -0000 [thread overview]
Message-ID: <AD04BD02-37F1-4C69-914B-47B58B069948@elis.ugent.be> (raw)
In-Reply-To: <bug-10004-3597-dF8jDtFSDR@http.sourceware.org/bugzilla/>
Is this the right place to report bug tracker spam?
Begin forwarded message:
> From: "jackie.rosen at hushmail dot com" <sourceware-bugzilla@sourceware.org>
> Date: 16 Feb 2014 19:27:41 GMT+01:00
> To: jonas.maebe@elis.ugent.be
> Subject: [Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=10004
>
> Jackie Rosen <jackie.rosen at hushmail dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |jackie.rosen at hushmail dot com
>
> --- Comment #5 from Jackie Rosen <jackie.rosen at hushmail dot com> ---
> *** Bug 260998 has been marked as a duplicate of this bug. ***
> Seen from the domain http://volichat.com
> Page where seen: http://volichat.com/adult-chat-rooms
> Marked for reference. Resolved as fixed @bugzilla.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
next parent reply other threads:[~2014-02-16 18:31 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 [this message]
[not found] ` <5301528A.2050302@gmail.com>
2014-02-17 8:01 ` Jan Kratochvil
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=AD04BD02-37F1-4C69-914B-47B58B069948@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--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