This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [downstream patch FYI] workaround stale frame_info * (PR 13866)
- From: Tom Tromey <tromey at redhat dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Pedro Alves <palves at redhat dot com>, gdb-patches at sourceware dot org
- Date: Wed, 06 Jun 2012 13:38:27 -0600
- Subject: Re: [downstream patch FYI] workaround stale frame_info * (PR 13866)
- References: <20120404191416.GA29603@host2.jankratochvil.net> <4FCE5B14.4030808@redhat.com> <20120605193920.GA19998@host2.jankratochvil.net>
Pedro> I've then ran the whole testsuite with this on, and that didn't catch
Pedro> any other problem. You mention in PR13866 many situations with stale
Pedro> frame_info; did you have some other way to catch those,
Jan> No. This single PR13866 crash and GDB code in general gives me enough
Jan> reasoning to believe:
Jan> (a) There exist other such crashes in GDB, just not tested by the
Jan> testsuite.
Jan> (b) More of such crashes will regress by changes in the future.
Jan> This is just my personal opinion you may not agree with.
Despite the difficulties perhaps we should try to write a static
analyzer for this. I am not sure if it could be made reliable enough,
but maybe it could. The problem cases are when the analyzer must
account for cleanups -- but in this case we might be able to get away
with ignoring them.
Another idea is to simply get rid of frame_info and have only a
frame_id-based API.
Tom