Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Maxim Grigoriev <maxim@tensilica.com>
Cc: gdb-patches@sources.redhat.com,
	Bob Wilson <bwilson@tensilica.com>,
		Marc Gauthier <marc@tensilica.com>,
		Chris Zankel <czankel@tensilica.com>
Subject: Re: Xtensa GDB port -- revised patch
Date: Sat, 11 Nov 2006 01:40:00 -0000	[thread overview]
Message-ID: <20061111014026.GA15921@nevyn.them.org> (raw)
In-Reply-To: <45552583.8070206@hq.tensilica.com>

On Fri, Nov 10, 2006 at 05:21:07PM -0800, Maxim Grigoriev wrote:
> I understood your concern is that the register number within the next 
> frame is not set ( *realnump ). On Xtensa, it's going to be unchanged 
> from the previous frame's value.
> 
> Question: is replacing of
> 
> frame_register_unwind (next_frame, regnum,
> optimizedp, lvalp, addrp, realnump, valuep);
> 
> with
> 
> *optimizedp = 0;
> *lvalp = lval_register;
> *addrp = 0;
> *realnump = regnum;
> if (valuep)
> frame_unwind_register (next_frame, (*realnump), valuep);
> 
> the fix you are looking for ? I tested it. It works fine.

Yes, I think that's right.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-11-11  1:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28  1:07 Maxim Grigoriev
2006-09-28  1:19 ` Daniel Jacobowitz
2006-10-05 23:55   ` Maxim Grigoriev
2006-10-06  9:51     ` Eli Zaretskii
2006-11-10 20:39     ` Daniel Jacobowitz
2006-11-11  1:21       ` Maxim Grigoriev
2006-11-11  1:40         ` Daniel Jacobowitz [this message]
2006-11-11  2:15           ` Maxim Grigoriev
     [not found]           ` <455530BB.3060403@hq.tensilica.com>
2006-11-14 21:54             ` Daniel Jacobowitz

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=20061111014026.GA15921@nevyn.them.org \
    --to=drow@false.org \
    --cc=bwilson@tensilica.com \
    --cc=czankel@tensilica.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=marc@tensilica.com \
    --cc=maxim@tensilica.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