From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 00/12] entryval: Fix x86_64 <optimized out> parameters, virtual tail call frames
Date: Tue, 19 Jul 2011 18:27:00 -0000 [thread overview]
Message-ID: <20110719181311.GA16667@host1.jankratochvil.net> (raw)
In-Reply-To: <m34o2i40py.fsf@fleche.redhat.com>
On Tue, 19 Jul 2011 19:52:25 +0200, Tom Tromey wrote:
> AX needs some big upgrades, or maybe an "AX 2.0" explicitly based on
> DWARF.
OK, thanks for the info.
> A related problem closer to home is that watchpoints don't respect
> location lists.
I at least filed it some time ago.
hardware watchpoint missed for -O2 -g inferior
http://sourceware.org/bugzilla/show_bug.cgi?id=11613
Jan
next prev parent reply other threads:[~2011-07-19 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 20:16 Jan Kratochvil
2011-07-19 16:39 ` Tom Tromey
2011-07-19 16:40 ` Jan Kratochvil
2011-07-19 18:17 ` Tom Tromey
2011-07-19 18:27 ` Jan Kratochvil [this message]
2011-07-19 18:44 ` Tom Tromey
2011-09-13 19:54 ` obsolete: " Jan Kratochvil
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=20110719181311.GA16667@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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