Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: fnf@redhat.com
Cc: jimb@redhat.com, fnf@ninemoons.com,
	gdb-patches@sources.redhat.com, Andrew Cagney <cagney@cygnus.com>,
	Michael Snyder <msnyder@cygnus.com>
Subject: Re: RFC: Avoid calling XXX_skip_prologue for assembly code
Date: Fri, 12 Apr 2002 08:34:00 -0000	[thread overview]
Message-ID: <3CB6FDCA.10E6C9F5@redhat.com> (raw)
In-Reply-To: <200204112330.g3BNUr827339@fred.ninemoons.com>

Fred,

May I suggest the creation of a set/show command to allow this
to be deactivated?

set assembly-skip-prolog

I don't mind if the default is off, I can put it in my .gdbinit file.
But disallowing it in a hardwired way will punish anyone who followed
the linkage conventions to be able to use backtrace.

I strongly object to this patch unless accompanied by a set/show 
command.  (But I am not the maintainer.)

Regards,
Fernando


Fred Fish wrote:
> 
> (Note: I'm revisiting an old patch submitted in Oct 2001)
> 
> > Would you be willing to try gdb.asm/asm-source.exp against a D10V sim
> > with this change?  I'm pretty sure your change is going to break that
> > test.  If so, you could fix the failure by changing the test to set
> > the breakpoint after the `enter' sequences.
> 
> I just built a D10V toolchain with a recent gdb, and ran the full
> testsuite with and without this change.  There was no difference in
> the testsuite results.  All of the asm-source.exp tests passed both
> with and without this patch installed.
> 
> OK to check in this patch?
> 
> -Fred

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2002-04-12 15:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 12:55 Fred Fish
2001-10-11 13:13 ` Jim Blandy
2001-10-11 13:37   ` Andrew Cagney
2001-10-11 13:22 ` Jim Blandy
2001-10-11 14:17 ` Jim Blandy
2001-10-11 15:40   ` Andrew Cagney
2001-10-11 19:23     ` Fred Fish
2002-04-11 16:30   ` Fred Fish
2002-04-12  8:34     ` Fernando Nasser [this message]
2002-04-12  9:41       ` Fred Fish
2002-04-12  9:47         ` Fernando Nasser
     [not found] ` <fnf@www.ninemoons.com>
2001-10-05 13:58   ` Kevin Buettner
2001-10-27 16:38   ` [RFA] Change auto-solib-add to boolean, add auto-solib-limit Kevin Buettner
2001-10-29 22:14   ` [RFA] Use 1024*1024 for a megabyte, not 1000000 Kevin Buettner
2001-10-30 17:22   ` [RFA] Fix a couple of auto-solib-add problems Kevin Buettner
2001-10-27 12:50 [RFA] Change auto-solib-add to boolean, add auto-solib-limit Fred Fish
2001-10-27 17:01 ` Elena Zannoni
2001-10-28  1:54 ` Eli Zaretskii
2001-10-29 20:35 [RFA] Use 1024*1024 for a megabyte, not 1000000 Fred Fish
2001-10-30 15:35 [RFA] Fix a couple of auto-solib-add problems Fred Fish
2001-10-31  4:02 ` Eli Zaretskii

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=3CB6FDCA.10E6C9F5@redhat.com \
    --to=fnasser@redhat.com \
    --cc=cagney@cygnus.com \
    --cc=fnf@ninemoons.com \
    --cc=fnf@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=msnyder@cygnus.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