public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "slyich at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/29450] run-low_high_pc.sh fails on i386 against binutils-2.39
Date: Sat, 06 Aug 2022 06:58:03 +0000	[thread overview]
Message-ID: <bug-29450-10460-LKdw0izczE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29450-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29450

--- Comment #2 from Sergei Trofimovich <slyich at gmail dot com> ---
Could it be that it's a mild `crti.o` corruption by new binutils? "MIPS
assembler" does not sound right.

```
$ readelf -aW crti.o --debug-dump
...
Contents of the .debug_info section:

  Compilation Unit @ offset 0x0:
   Length:        0x49 (32-bit)
   Version:       2
   Abbrev Offset: 0x0
   Pointer Size:  4
 <0><b>: Abbrev Number: 1 (DW_TAG_compile_unit)
    <c>   DW_AT_stmt_list   : (data4) 0x0
    <10>   DW_AT_ranges      : (data4) 0x0
    <14>   DW_AT_name        : (strp) (offset: 0x0): ../sysdeps/i386/crti.S
    <18>   DW_AT_comp_dir    : (strp) (offset: 0x17): /build/glibc-2.35/csu
    <1c>   DW_AT_producer    : (strp) (offset: 0x2d): GNU AS 2.39
    <20>   DW_AT_language    : (data2) 32769    (MIPS assembler)
 <1><22>: Abbrev Number: 2 (DW_TAG_subprogram)
    <23>   DW_AT_name        : (strp) (offset: 0x39): _init
    <27>   DW_AT_external    : (flag) 1
    <28>   DW_AT_low_pc      : (addr) 0x0
    <2c>   DW_AT_high_pc     : (addr) 0x0
 <1><30>: Abbrev Number: 2 (DW_TAG_subprogram)
    <31>   DW_AT_name        : (strp) (offset: 0x3f): __x86.get_pc_thunk.bx
    <35>   DW_AT_external    : (flag) 1
    <36>   DW_AT_low_pc      : (addr) 0x0
    <3a>   DW_AT_high_pc     : (addr) 0x4
 <1><3e>: Abbrev Number: 2 (DW_TAG_subprogram)
    <3f>   DW_AT_name        : (strp) (offset: 0x55): _fini
    <43>   DW_AT_external    : (flag) 1
    <44>   DW_AT_low_pc      : (addr) 0x0
    <48>   DW_AT_high_pc     : (addr) 0x0
 <1><4c>: Abbrev Number: 0
...

```

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-08-06  6:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06  6:34 [Bug libdw/29450] New: " slyich at gmail dot com
2022-08-06  6:47 ` [Bug libdw/29450] " slyich at gmail dot com
2022-08-06  6:58 ` slyich at gmail dot com [this message]
2022-08-06  8:06 ` slyich at gmail dot com
2022-08-06  8:10 ` slyich at gmail dot com
2022-08-06  8:10 ` slyich at gmail dot com
2022-08-07 23:30 ` mark at klomp dot org
2022-08-10 11:13 ` mark at klomp dot org
2022-08-10 11:15 ` mliska at suse dot cz
2022-08-11  9:17 ` slyich at gmail dot com

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=bug-29450-10460-LKdw0izczE@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).