Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC 2/5] Frame unwinding using struct value
Date: Fri, 04 Apr 2008 19:10:00 -0000	[thread overview]
Message-ID: <20080404172214.GD23283@adacore.com> (raw)
In-Reply-To: <20080331221024.GA22334@caradoc.them.org>

> +struct value *
> +frame_unwind_register_value (struct frame_info *frame, int regnum)
> +{
> +  struct value *value;
> +
> +  if (frame_debug)
> +    {
> +      fprintf_unfiltered (gdb_stdlog, "\
> +{ frame_unwind_register_value (frame=%d,regnum=%d(%s),...) ",
> +			  frame->level, regnum,
> +			  frame_map_regnum_to_name (frame, regnum));
> +    }
> +
> +  gdb_assert (frame != NULL);

The gdb_assert should be moved up before the "if (frame_debug)" block.
Otherwise, we'll bomb while dereferencing FRAME before we trip the
assertion. (I realize that this code was already like this before)

Other than that, I tried to read it as carefully as possible and
grasp as much of the big picture as I could, and it looked good
to me.

I can help with the conversion of some of the targets: hppa, ia64,
mips (but it would be better if someone having access to mips-linux
did it for me, mips-irix results are not stellar right now), powerpc,
and sparc. I can't test alpha anymore, for some reason dejagnu no
longer works on our Tru64 machines :-(.

-- 
Joel


  parent reply	other threads:[~2008-04-04 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 22:12 Daniel Jacobowitz
2008-04-01 13:23 ` Eli Zaretskii
2008-04-17 15:30   ` Daniel Jacobowitz
2008-04-04 19:10 ` Joel Brobecker [this message]
2008-04-17 15:59   ` Daniel Jacobowitz
2008-04-04 19:16 ` Joel Brobecker
2008-04-07 19:34 ` Thiago Jung Bauermann
2008-04-17 16:02   ` Daniel Jacobowitz
2008-04-30 23:31 ` Daniel Jacobowitz
     [not found]   ` <20080430230012.GB3801@adacore.com>
2008-05-01  3:37     ` 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=20080404172214.GD23283@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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