From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA/ada] Improve is_known_support_routine
Date: Mon, 08 Jan 2007 03:30:00 -0000 [thread overview]
Message-ID: <20070108033030.GB537@adacore.com> (raw)
In-Reply-To: <20070107233832.GB28585@nevyn.them.org>
> > The is_known_support_routine identifies any frame for which we cannot
> > find the source file. The check we currently have in place is a bit too
> > simplistic, so I replaced it with the function we use to locate source
> > files:
> >
> > - if (stat (sal.symtab->filename, &st))
> > + if (symtab_to_fullname (sal.symtab) == NULL)
>
> Fine with me, although I wonder if "the source is missing" is really
> the concept you want. Why should whether source for the runtime
> library is present determine what we show? That would make the
> feature more awkward to use for people who built their own libgnat and
> still have the build tree.
Actually, when I worked on cleaning up that routine, I found that
the attached comment was a bit incomplete. Here the new comment
explaining the main reason for discarding that frame:
/* If there is a symtab, but the associated source file cannot be
located, then assume this is not user code: Selecting a frame
for which we cannot display the code would not be very helpful
for the user. This should also take care of case such as VxWorks
where the kernel has some debugging info provided for a few units. */
if (symtab_to_fullname (sal.symtab) == NULL)
return 1;
In terms of the people building their own libgnat, it is true that
this might make it a bit more awkward for them. This is not necessarily
true that they would want in this case the debugger to select a frame
inside the runtime. So we tried to find a compromise based on our own
usage and user feedback that was the most helpful in most cases.
--
Joel
prev parent reply other threads:[~2007-01-08 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 18:26 Joel Brobecker
2007-01-07 7:14 ` Joel Brobecker
2007-01-07 23:38 ` Daniel Jacobowitz
2007-01-08 3:30 ` Joel Brobecker
2007-01-08 3:30 ` Joel Brobecker [this message]
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=20070108033030.GB537@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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