Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [6] What if EXTRA_FRAME_INFO wasn't required
Date: Tue, 08 Apr 2003 22:08:00 -0000	[thread overview]
Message-ID: <3E93483A.9000102@redhat.com> (raw)
In-Reply-To: <20030331223213.GF916@gnat.com>

> 
> Will try it out. I also identified a few macros that were not converted
> yet, but all of them should be easy to do, except one (FIX_CALL_DUMMY)
> which I understand should be replaced in the relatively near future.

I need to find an excuse for doing it.  Something as perverted as 
modifying the d10v to use generic dummy frames that are on the stack 
should do the trick :-)

I'm guessing that the entire dummy mess can be replaced with a single 
simple:

	push_dummy_breakpoint()

with a default implementation looking something like:

	BREAKPOINT_FROM_PC(addr, len, bytes);
	write_memory (addr, len, bytes);

> Can I commit your patch if it turns out to be working, or would you
> prefer to do it?

I've committed the bulk of it.  Suggest giving multi-arch partial a 
wirl.  Oh, I thought I glimpsed some ->frame or ->pc references in some 
of the HP code :-(

Andrew



  parent reply	other threads:[~2003-04-08 22:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 21:34 Andrew Cagney
2003-03-28 21:39 ` Joel Brobecker
2003-03-31  0:18   ` Andrew Cagney
2003-03-31 22:32     ` Joel Brobecker
2003-03-31 23:36       ` Andrew Cagney
2003-04-08 22:08       ` Andrew Cagney [this message]
2003-04-08 22:17         ` Joel Brobecker
2003-03-31 22:24 ` Joel Brobecker

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=3E93483A.9000102@redhat.com \
    --to=ac131313@redhat.com \
    --cc=brobecker@gnat.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