From: "Eli Zaretskii" <eliz@gnu.org>
To: David Lecomber <david@streamline-computing.com>
Cc: "gdb-patches@sources.redhat.com"
<1099347096.31287.3.camel@cpc1-oxfd5-5-0-cust86.oxfd.cable.ntl.com>
(message from David Lecomber on Mon, 01 Nov 2004 22:11:36 +0000)
Subject: Re: [PATCH] Seg fault whilst stepping when watch set [ping!] [in breakpoint.c]
Date: Tue, 02 Nov 2004 04:38:00 -0000 [thread overview]
Message-ID: <01c4c095$Blat.v2.2.2$3f440920@zahav.net.il> (raw)
In-Reply-To: <1098720391.1935.0.camel@delmo.priv.wark.uk.streamline-computing.com>
> From: David Lecomber <david@streamline-computing.com>
> Date: Mon, 01 Nov 2004 22:11:36 +0000
>
> Two week ping!!!! This really is an obviously harmless patch, not
> necessarily an obvious patch, but it's one that can only stop a segfault
> that would otherwise happen, so could someone give the ok please..
Sorry, I missed the original post somehow.
Can you post a short test program, preferably in C, that can be used
to reproduce this problem? I don't think I've ever seen such crashes.
TIA
next prev parent reply other threads:[~2004-11-02 4:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 0:09 [PATCH] Seg fault whilst stepping when watch set David Lecomber
2004-10-25 16:10 ` [PATCH] Seg fault whilst stepping when watch set [ping!] David Lecomber
2004-11-01 22:05 ` [PATCH] Seg fault whilst stepping when watch set [ping!] [in breakpoint.c] David Lecomber
2004-11-02 4:38 ` Eli Zaretskii [this message]
[not found] ` <1099385491.31287.19.camel@cpc1-oxfd5-5-0-cust86.oxfd.cable.ntl.com>
2004-11-02 21:40 ` Eli Zaretskii
2004-11-03 12:08 ` David Lecomber
2004-11-17 21:38 ` David Lecomber
2004-11-03 18:09 ` Eli Zaretskii
[not found] <01c4cef8$Blat.v2.2.2$3fd12960@zahav.net.il>
2004-11-21 0:24 ` David Lecomber
2004-11-21 0:42 ` Daniel Jacobowitz
2004-11-21 5:29 ` Eli Zaretskii
2004-11-21 6:48 ` Daniel Jacobowitz
2004-11-21 5:19 ` Eli Zaretskii
2004-11-21 6:49 ` Daniel Jacobowitz
2004-11-21 10:36 ` David Lecomber
2004-11-21 19:40 ` Eli Zaretskii
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='01c4c095$Blat.v2.2.2$3f440920@zahav.net.il' \
--to=eliz@gnu.org \
--cc=1099347096.31287.3.camel@cpc1-oxfd5-5-0-cust86.oxfd.cable.ntl.com \
--cc=david@streamline-computing.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