Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] KFAIL gdb/1025
Date: Fri, 07 Feb 2003 17:40:00 -0000	[thread overview]
Message-ID: <200302071740.h17HeD716326@duracef.shout.net> (raw)

Perhaps there is a $PATH / build issue.  Check 'gcj --version' and also
check that the directory where you installed your gcc 3.1 has a
gcj binary in it.

I am guessing that you built your gcc 3.1 without gcj and that you are
picking up the base gcj on your system.  Or maybe you have some
uberbaum-ish tree and runtest is messing with $PATH as well.

  spawn gcj ./gdb.java/jmisc.java --main=jmisc -g -o /extra/gdb/mirror/src/gdb/testsuite/gdb.java/jmisc 
  /tmp/ccezwoW0.s: Assembler messages:
  /tmp/ccezwoW0.s:28: Warning: .stabs: description field '10001' too big, try a different debug format
  /tmp/ccezwoW0.s:57: Warning: .stabs: description field '60004' too big, try a different debug format

There's definitely no '-gstabs+' there, and definitely '.stabs' warning
messages.  Strange.

Michael C


             reply	other threads:[~2003-02-07 17:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07 17:40 Michael Elizabeth Chastain [this message]
2003-02-07 17:46 ` David Carlton
  -- strict thread matches above, loose matches on Subject: below --
2003-02-07 17:08 Michael Elizabeth Chastain
2003-02-07 17:13 ` David Carlton
2003-02-07 16:16 Michael Elizabeth Chastain
2003-02-07 17:04 ` David Carlton
2003-02-05  6:04 Michael Elizabeth Chastain
2003-02-04 20:07 Michael Elizabeth Chastain
2003-02-04 18:33 Michael Elizabeth Chastain
2003-02-04 15:32 Michael Elizabeth Chastain
2003-02-04  1:18 David Carlton
2003-02-04 14:44 ` Daniel Jacobowitz
2003-02-04 17:17   ` David Carlton
2003-02-04 17:22     ` Daniel Jacobowitz
2003-02-04 22:28     ` David Carlton
2003-02-06 20:59       ` David Carlton

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=200302071740.h17HeD716326@duracef.shout.net \
    --to=mec@shout.net \
    --cc=carlton@math.stanford.edu \
    --cc=drow@mvista.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