public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Duane Ellis <duane_ellis@franklin.com>
To: insight@sourceware.cygnus.com
Subject: Tail Calls & Insight
Date: Tue, 16 May 2000 12:43:00 -0000	[thread overview]
Message-ID: <200005161943.PAA05435@mercury.franklin.com> (raw)

I'm working on a custom port for insight/gdb for our custom RISC cpu
and I'm having a problem with something.

When you click the 'next' button, GDB really single steps till the PC
goes somewhere expected, or unexpected.

If it's unexpected (ie: a subroutine call occurs) GDB then assumes
that the return address is on the stack and pops the return address,
sets a new breakpoint and 'runs', hoping it will hit the breakpoint.

Unfortunatly, (or fortunatly depending on your view) one optmization
trick we use is to convert tail calls into jumps.

Is there any way of describing this situation to GDB?

-Duane.

             reply	other threads:[~2000-05-16 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-16 12:43 Duane Ellis [this message]
2000-05-16 12:47 ` Tom Tromey

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=200005161943.PAA05435@mercury.franklin.com \
    --to=duane_ellis@franklin.com \
    --cc=insight@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).