This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [commit] Yet another get_frame_arch (NULL) call
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Ulrich Weigand <uweigand at de dot ibm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 15 Jan 2009 15:15:50 +0400
- Subject: Re: [commit] Yet another get_frame_arch (NULL) call
- References: <200901131803.n0DI3hfN010337@d12av02.megacenter.de.ibm.com>
> we found another case where get_frame_arch (NULL) was called:
Is there a way we can help you track these calls down? Or are
we supposed to have them all tracked down by now? I'm just wondering
if the addition of a warning or, more strongly, an assert might
help avoiding re-introducing this issue.
BTW: Perhaps we should document more explicitly the fact that this
routine should be given a non-null frame? The current implementation
is such that a NULL frame doesn't really matter, but otherwise,
I fear that we'll undo part of what you're doing now.
--
Joel