From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [downstream patch FYI] workaround stale frame_info * (PR 13866)
Date: Fri, 18 May 2012 18:04:00 -0000 [thread overview]
Message-ID: <20120518180433.GA5305@host2.jankratochvil.net> (raw)
In-Reply-To: <4FB68E47.1080903@redhat.com>
On Fri, 18 May 2012 20:00:39 +0200, Pedro Alves wrote:
> It seems to me that combining the both points, we should be able to get back
> the old behavior, where calling a breakpoint insertion function wouldn't
> invalidate the frame chain.
This is not well debuggable compared to the Tom's compile-time verification
proposal. There may be workforce to mechanically replace frame_info for
frame_id as long as it gets reviewed.
Regards,
Jan
next prev parent reply other threads:[~2012-05-18 18:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 19:14 Jan Kratochvil
2012-05-18 17:44 ` Tom Tromey
2012-05-18 18:01 ` Pedro Alves
2012-05-18 18:04 ` Jan Kratochvil [this message]
2012-05-18 19:16 ` Tom Tromey
2012-06-05 19:17 ` Pedro Alves
2012-06-05 19:39 ` Jan Kratochvil
2012-06-05 19:41 ` Pedro Alves
2012-06-05 19:50 ` Pedro Alves
2012-06-06 19:38 ` Tom Tromey
2012-06-06 20:16 ` Pedro Alves
2012-06-05 19:24 ` Pedro Alves
2012-06-05 19:52 ` Pedro Alves
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=20120518180433.GA5305@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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