From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: gcc@gcc.gnu.org
Subject: Regressions with dwarf debugging
Date: Sun, 14 Jun 2009 03:14:00 -0000 [thread overview]
Message-ID: <20090614031436.GA5909@troutmask.apl.washington.edu> (raw)
Someone has broken gfortran on FreeBSD with dwarf debugging.
This is a regression. Please fix!
Testing debug/trivial.f, -gdwarf-21
Executing on host: /usr/home/kargl/gcc/obj4x/gcc/testsuite/gfortran/../../gfortr
an -B/usr/home/kargl/gcc/obj4x/gcc/testsuite/gfortran/../../ /usr/home/kargl/gcc
/gcc4x/gcc/testsuite/gfortran.dg/debug/trivial.f -gdwarf-21 -S -o trivial.s
(timeout = 300)
f951: error: dwarf version 21 is not supported
compiler exited with status 1
output is:
f951: error: dwarf version 21 is not supported
FAIL: gfortran.dg/debug/trivial.f -gdwarf-21 (test for excess errors)
Excess errors:
f951: error: dwarf version 21 is not supported
Testing debug/trivial.f, -gdwarf-2
Testing debug/trivial.f, -gdwarf-23
Executing on host: /usr/home/kargl/gcc/obj4x/gcc/testsuite/gfortran/../../gfortran -B/usr/home/kargl/gcc/obj4x/gcc/testsuite/gfortran/../../ /usr/home/kargl/gcc/gcc4x/gcc/testsuite/gfortran.dg/debug/trivial.f -gdwarf-23 -S -o trivial.s (timeout = 300)
f951: error: dwarf version 23 is not supported
compiler exited with status 1
output is:
f951: error: dwarf version 23 is not supported
FAIL: gfortran.dg/debug/trivial.f -gdwarf-23 (test for excess errors)
Excess errors:
f951: error: dwarf version 23 is not supported
testcase /usr/home/kargl/gcc/gcc4x/gcc/testsuite/gfortran.dg/debug/debug.exp completed in 1 seconds
Running /usr/home/kargl/gcc/gcc4x/gcc/testsuite/gfortran.dg/dg.exp ...
--
Steve
next reply other threads:[~2009-06-14 3:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 3:14 Steve Kargl [this message]
2009-06-15 2:38 ` Michael Meissner
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=20090614031436.GA5909@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).