public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/13415] Invalid breakpoints when linking with --gc-sections
Date: Tue, 11 Jan 2022 17:30:59 +0000	[thread overview]
Message-ID: <bug-13415-4717-1XKy3YTFeh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13415-4717@http.sourceware.org/bugzilla/>

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

--- Comment #9 from Tom Tromey <tromey at sourceware dot org> ---
Note there's also bug #12528 on this topic.  And, patches did go in
to fix some problems with --gc-sections.

In the program that fails for me, the CU looks like:

 <0><199f>: Abbrev Number: 2 (DW_TAG_compile_unit)
    <19a0>   DW_AT_producer    : (indirect string, offset: 0x27da): GNU Ada
11.2.1 20210728 (Red Hat 11.2.1-1) -O -gnatez -gnatea -g -ffunction-sections
-gnatez -mtune=generic -march=x86-64
    <19a4>   DW_AT_language    : 13     (ADA 95)
    <19a5>   DW_AT_name        : (indirect line string, offset: 0x10d):
pack.adb
    <19a9>   DW_AT_comp_dir    : (indirect line string, offset: 0x0):
/home/tromey/AdaCore/gdb-testsuite/tests/KB21-043__bp_next_to_generic_fun
    <19ad>   DW_AT_ranges      : 0x63
    <19b1>   DW_AT_low_pc      : 0x0
    <19b9>   DW_AT_stmt_list   : 0x29e


low_pc == 0x0 is fishy, especially considering this is a native
Linux executable and not some embedded thing where it might make sense.

Also in the ranges:

    00000063 0000000000000000 000000000000003d 
    0000006d <End of list>

which is also pretty weird.

Maybe gdb ought to reject this entire CU, at least for purposes of
the line table.

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

  parent reply	other threads:[~2022-01-11 17:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 13:27 [Bug breakpoints/13415] New: " steffen-schmidt at siemens dot com
2011-11-16 13:28 ` [Bug breakpoints/13415] " steffen-schmidt at siemens dot com
2011-11-16 13:28 ` steffen-schmidt at siemens dot com
2011-11-16 13:30 ` steffen-schmidt at siemens dot com
2011-11-16 20:53 ` tromey at redhat dot com
2011-11-17  7:41 ` steffen-schmidt at siemens dot com
2011-11-17 15:15 ` tromey at redhat dot com
2011-11-21  7:46 ` steffen-schmidt at siemens dot com
2012-01-25 17:26 ` tromey at redhat dot com
2022-01-07 21:54 ` tromey at sourceware dot org
2022-01-11 17:30 ` tromey at sourceware dot org [this message]
2022-01-11 17:32 ` tromey at sourceware dot org
2022-01-11 18:20 ` tromey at sourceware dot org
2024-03-15  9:16 ` sam at gentoo dot org

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-13415-4717-1XKy3YTFeh@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).