Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch, rfc, 6] Check for "main" in minimal symbols in BT
Date: Mon, 07 Jul 2003 21:07:00 -0000	[thread overview]
Message-ID: <20030707210756.GA19339@nevyn.them.org> (raw)
In-Reply-To: <3F09DB1D.6070003@redhat.com>

On Mon, Jul 07, 2003 at 04:42:05PM -0400, Andrew Cagney wrote:
> Hello,
> 
> This patch extends the inside_main_func() check so that, when "main" 
> isn't found in the symbol table,  the mimimal symbol table is searched. 
>  In case you're wondering, the logic for finding the end address of 
> "main" was cobbled together from random bits of code from blockframe and 
> the alpha.  It certainly appears to work for d10v and i386.
> 
> Anyway, with this, the d10v's assembler backtrace stops at main goving 
> the short 'n' sharp backtrace
> 
> 	foo2
> 	main
> 
> instead of the current:
> 
> 	foo2
> 	main
> 	_start
> 	_start
> 
> The patch (since things now stop in "main") also removes the d10v 
> specific frame ID eq test; and updates the testsuite so that it doesn't 
> allow "_start" in the backtrace.
> 
> I intend checking this into both 6.0 branch and mainline in a few days.

Definitely like the patch!  Should we make inside_entry_func also check
the minimal symbol table?  Since we have the entry point PC reliably
(via ELF headers).

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-07-07 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-07 20:42 Andrew Cagney
2003-07-07 21:07 ` Daniel Jacobowitz [this message]
2003-07-08 20:44   ` Andrew Cagney
2003-07-08 21:55     ` Daniel Jacobowitz
2003-07-15 17:31 ` Andrew Cagney

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=20030707210756.GA19339@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.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