From: Greg Law <glaw@undo-software.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb-6.8 branchpoint
Date: Tue, 26 Feb 2008 22:02:00 -0000 [thread overview]
Message-ID: <47C48B2B.2040302@undo-software.com> (raw)
In-Reply-To: <20080226213741.GC3894@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
Hi Joel,
As per earlier on-list discussion, any chance of applying this simple
fix to prevent random SEGV's in gdb?
Cheers,
Greg
Joel Brobecker wrote:
> Hello,
>
> Now that the last known blocking issue has been dealt with, I think
> a good branchpoint would be: "2008-02-26 10:00". That's today shortly
> after Vladimir checked Nick's change in.
>
> Unless there are some objections (or other suggestions!), I'll create
> the branch later this week, and start the release process.
>
--
Greg Law, Undo Software http://undo-software.com/
[-- Attachment #2: regcache_fix.patch --]
[-- Type: text/x-patch, Size: 658 bytes --]
Index: gdb/regcache.c
===================================================================
RCS file: /cvs/src/src/gdb/regcache.c,v
retrieving revision 1.163
diff -u -r1.163 regcache.c
--- gdb/regcache.c 1 Jan 2008 22:53:12 -0000 1.163
+++ gdb/regcache.c 4 Feb 2008 22:24:32 -0000
@@ -472,6 +472,9 @@
regcache_xfree (current_regcache);
current_regcache = NULL;
+ /* Need to forget about any frames we have cached, too. */
+ reinit_frame_cache ();
+
/* Force cleanup of any alloca areas if using C alloca instead of
a builtin alloca. This particular call is used to clean up
areas allocated by low level target code which may build up
next prev parent reply other threads:[~2008-02-26 21:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 21:54 Joel Brobecker
2008-02-26 21:57 ` Thiago Jung Bauermann
2008-02-26 22:25 ` Daniel Jacobowitz
2008-02-26 22:26 ` Thiago Jung Bauermann
2008-02-26 22:30 ` Joel Brobecker
2008-02-26 22:02 ` Greg Law [this message]
2008-02-26 22:37 ` Joel Brobecker
2008-02-27 0:26 ` Michael Snyder
2008-02-27 2:55 ` Daniel Jacobowitz
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=47C48B2B.2040302@undo-software.com \
--to=glaw@undo-software.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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