public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: gdb@sources.redhat.com
Subject: Inferior function call command set
Date: Thu, 01 May 2003 20:55:00 -0000	[thread overview]
Message-ID: <3EB16A02.9080904@redhat.com> (raw)

Hello,

GDB has a number of commands for controlling the behavior of inferior 
function calls (developers think of them as call dummies).  Looking in 
"infcall.c" I find:

	set/show coerce-float-to-double yes|no
	set/show unwindonsignal yes|no

And I'm now looking to add a third:

	set/show call-location on-stack|at-start|auto

So:

- anyone got a better name for this new command?

- should these be re-grouped into a set of sub commands vis:

	set/show call coerce-float-to-double yes|no
	set/show call unwind-on-signal yes|no
	set/show call breakpoint-location on-stack|at-entry|auto

I'm figuring that "(gdb) set call" should provide a rough correspondance 
to the existing "(gdb) call" command.

Comment away ...

Andrew

PS: Yes, this means that I've got a target using generic dummy frames 
where the return breakpoint is on the stack.

PPS: While it doesn't currently work, it should be possible to make 
on-stack function when the stack has no-execute set.  It would lead to a 
SIGSEG (instead of a SIGTRAP) which GDB should then map onto a breakpoint.

             reply	other threads:[~2003-05-01 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 20:55 Andrew Cagney [this message]
2003-05-01 21:12 ` Doug Evans
2003-05-01 21:28   ` Andrew Cagney
2003-05-01 21:49     ` Doug Evans
2003-05-01 22:48       ` Andrew Cagney
2003-05-01 23:00         ` Doug Evans

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=3EB16A02.9080904@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).