Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Greg Law <glaw@undo-software.com>
Cc: gdb-patches@sourceware.org
Subject: Re: SIGSEGV on gdb 6.7*
Date: Mon, 04 Feb 2008 22:11:00 -0000	[thread overview]
Message-ID: <20080204221036.GA26939@caradoc.them.org> (raw)
In-Reply-To: <47A78A92.8000501@undo-software.com>

On Mon, Feb 04, 2008 at 09:58:42PM +0000, Greg Law wrote:
> Should it be just flushregs that invalidates the frame cache, or should  
> it happen from registers_changed()?

Good question :-)  Probably registers_changed, but I suspect that
makes a lot of other reinit_frame_cache calls redundant.

In the long term there should be more than a single register cache,
and more than a single frame cache - one per thread, for instance.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-02-04 22:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 20:50 Greg Law
2008-02-04 21:04 ` Daniel Jacobowitz
2008-02-04 21:39   ` Greg Law
     [not found]   ` <47A7850B.10202@undo-software.com>
2008-02-04 21:45     ` Daniel Jacobowitz
2008-02-04 21:59       ` Greg Law
2008-02-04 22:11         ` Daniel Jacobowitz [this message]
2008-02-04 22:36           ` Greg Law
2008-02-11 20:59             ` Greg Law
2008-02-26 23:00 ` Michael Snyder
2008-02-27  0:37   ` Daniel Jacobowitz
2008-02-27  0:43     ` Michael Snyder
2008-02-27  0:51       ` Daniel Jacobowitz
2008-02-27  0:54         ` Michael Snyder
2008-02-27  1:05           ` Daniel Jacobowitz
2008-02-27  1:08             ` Michael Snyder
2008-02-27 20:23               ` Greg Law
2008-02-28  7:46                 ` Vladimir Prus
2008-02-28 14:17                   ` Daniel Jacobowitz
2008-02-28 14:17                   ` Thiago Jung Bauermann
2008-02-28 16:18                     ` Daniel Jacobowitz
2008-03-04 20:09               ` 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=20080204221036.GA26939@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=glaw@undo-software.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