Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: Ulrich.Weigand@de.ibm.com, gdb-patches@sources.redhat.com
Subject: [patch] dw2-ranges.S non-g GAS crash  [Re: spu-as internal error]
Date: Mon, 07 Apr 2008 11:47:00 -0000	[thread overview]
Message-ID: <20080407063027.GA26788@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20080407040340.GF1446@bubble.grove.modra.org>

[-- Attachment #1: Type: text/plain, Size: 853 bytes --]

On Mon, 07 Apr 2008 06:03:40 +0200, Alan Modra wrote:
> Ulrich Weigand wrote:
> > building the file gdb.dwarf2/dw2-ranges.S from the GDB test suite results
> > in an internal error in spu-as (current SDK CVS version):
> > 
> > /home/uweigand/fsf/gdb-head/gdb/testsuite/gdb.dwarf2/dw2-ranges.S:40:
> > Internal error, aborting at ../../binutils-2.18.50/gas/dwarf2dbg.c line
> > 1675 in out_debug_info
> > Please report this bug.
> 
> Has this testcase ever assembled?  On any target?  I think gas would
> always have aborted unless you pass -g to gas or supply .file
> directives.

It was always built just inside `runtest'.

Requesting a commit approval.  Verified unpatched GDB still FAILs on it.


(Still aware / going to post the fix to the STABS regression by this patch:
	http://sourceware.org/ml/gdb-patches/2007-12/msg00248.html
)


Regards,
Jan

[-- Attachment #2: dw2ranges-file.patch --]
[-- Type: text/plain, Size: 645 bytes --]

2008-04-07  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.dwarf2/dw2-ranges.S: New stub `.file' directive.

--- ./gdb/testsuite/gdb.dwarf2/dw2-ranges.S	1 Jan 2008 22:53:19 -0000	1.2
+++ ./gdb/testsuite/gdb.dwarf2/dw2-ranges.S	7 Apr 2008 06:24:13 -0000
@@ -19,6 +19,9 @@
    DW_AT_ranges as the linker could place both sections at arbitrary locations.
    */
 
+	/* Such directive is required by GAS for builds without `-g'.  */
+	.file	1 "dw2-ranges.S"
+
 	/* Without this directive GAS will not emit DWARF2 unless we provide an
 	   instruction to assemble.  We want to avoid any instructions to
 	   remain architecture independent.  */

       reply	other threads:[~2008-04-07  6:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF789B1703.6C47E7DB-ONCA257424.0010854A-E9257424.00108D3E@au1.ibm.com>
     [not found] ` <20080407040340.GF1446@bubble.grove.modra.org>
2008-04-07 11:47   ` Jan Kratochvil [this message]
2008-04-08  5:42     ` Ulrich Weigand
2008-04-08  7:56       ` Jan Kratochvil
2008-04-14 19:08     ` 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=20080407063027.GA26788@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=amodra@bigpond.net.au \
    --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