Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: SH patch 2 (was Re: [RFA] SH: Deprecate deprecated functions, use new frame interface)
Date: Mon, 22 Sep 2003 14:33:00 -0000	[thread overview]
Message-ID: <20030922143254.GR9981@cygbert.vinschen.de> (raw)
In-Reply-To: <20030916173038.GA25459@nevyn.them.org>

On Tue, Sep 16, 2003 at 01:30:38PM -0400, Daniel Jacobowitz wrote:
> On Tue, Sep 16, 2003 at 07:26:06PM +0200, Corinna Vinschen wrote:
> > FAIL: gdb.base/store.exp: print add  - charest
> > FAIL: gdb.base/store.exp: print add  - short
> > FAIL: gdb.base/store.exp: print old r - longest
> > FAIL: gdb.base/store.exp: print old r - double
> > FAIL: gdb.base/store.exp: print old r - doublest
> > FAIL: gdb.base/store.exp: up print old r - longest
> > FAIL: gdb.base/store.exp: up print old r - double
> > FAIL: gdb.base/store.exp: up print old r - doublest
> 
> Hmm, with the current state of the tree those failures are pretty
> surprising.  Especially if you turned on the dwarf2 unwinder, they
> shouldn't be there.

Hmm, I'm getting a bunch of "Unhandled dwarf expression opcode"
messages.  The opcode in question is 0x93, DW_OP_piece.  I tweaked
the error message in dwarf2expr.c::execute_stack_op() to print the
opcode as well, so what I get is e.g. this:

  [...]
  continue^M
  Continuing.^M
  wack_longest (u=Unhandled dwarf expression opcode: 0x93^M
  ) at /home/corinna/src/gdb/src/gdb/testsuite/gdb.base/store.c:101^M
  101       register longest l = u, r = v;^M
  (gdb) PASS: gdb.base/store.exp: continue to wack_longest
  next^M
  102       l = add_longest (l, r);^M
  (gdb) PASS: gdb.base/store.exp: next longest
  print l^M
  $17 = -1^M
  (gdb) PASS: gdb.base/store.exp: print old l - longest
  print r^M
  Unhandled dwarf expression opcode: 0x93^M
  (gdb) FAIL: gdb.base/store.exp: print old r - longest

What does that mean?  How does that affect the approval of my code
as it is now?

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.


  parent reply	other threads:[~2003-09-22 14:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 16:55 [RFA] SH: Deprecate deprecated functions, use new frame interface Corinna Vinschen
2003-09-12 17:32 ` Elena Zannoni
2003-09-15 15:53   ` SH patch 1 (was Re: [RFA] SH: Deprecate deprecated functions, use new frame interface) Corinna Vinschen
2003-09-16 15:42     ` Elena Zannoni
2003-09-16 15:57       ` Corinna Vinschen
2003-09-15 16:01   ` SH patch 2 " Corinna Vinschen
2003-09-16 17:06     ` Elena Zannoni
2003-09-16 17:26       ` Corinna Vinschen
2003-09-16 17:30         ` Daniel Jacobowitz
2003-09-16 17:58           ` Corinna Vinschen
2003-09-22 14:33           ` Corinna Vinschen [this message]
2003-09-22 14:44             ` Daniel Jacobowitz
2003-09-22 15:08               ` Corinna Vinschen
2003-09-23 20:16                 ` Elena Zannoni
2003-09-24  8:43                   ` Corinna Vinschen
2003-09-24 11:28                     ` Corinna Vinschen
2003-09-25 19:44                       ` Elena Zannoni
2003-09-26 11:32                         ` Corinna Vinschen
2003-09-24 18:12                     ` Elena Zannoni
2003-09-25  8:56                       ` Corinna Vinschen
2003-09-22 16:27               ` Andrew Cagney

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=20030922143254.GR9981@cygbert.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=gdb-patches@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