Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/breakpoint] Handle setting breakpoint on label without address
Date: Thu, 27 Aug 2020 13:41:29 +0100	[thread overview]
Message-ID: <23b43acc-9846-a03c-5207-3ae80efc1d6f@palves.net> (raw)
In-Reply-To: <20200827115217.GA17450@delia.home>

On 8/27/20 12:52 PM, Tom de Vries wrote:
> Hi,
> 
> Consider test-case test.c:
> ...
> $ cat test.c
> int main (void) {
>   return 0;
>  L1:
>   (void)0;
> }
> ...
> 
> Compiled with debug info:
> ...
> $ gcc test.c -g
> ...
> 
> When attempting to set a breakpoint at L1, which is a label without address:
> ...
>  <1><f4>: Abbrev Number: 2 (DW_TAG_subprogram)
>     <f5>   DW_AT_name        : main
>  <2><115>: Abbrev Number: 3 (DW_TAG_label)
>     <116>   DW_AT_name        : L1
>     <119>   DW_AT_decl_file   : 1
>     <11a>   DW_AT_decl_line   : 5
>  <2><11b>: Abbrev Number: 0

Is this a debug info bug, or is the debug info telling us that the
address of the label is the same as the line number's address?

How about looking up the line number address instead of throwing
an error?


  reply	other threads:[~2020-08-27 12:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 11:52 Tom de Vries
2020-08-27 12:41 ` Pedro Alves [this message]
2020-08-27 13:49   ` Tom de Vries
2020-08-28 10:31     ` Tom de Vries
2020-08-28 13:20       ` [PATCH][gdb/breakpoint, PIE] " Tom de Vries
2020-09-03 10:34         ` [committed][PATCH][gdb/breakpoint, " Tom de Vries
2020-08-28 13:32     ` [PATCH][gdb/breakpoint] " Pedro Alves
2020-08-28 13:53       ` Tom de Vries
2020-08-28 14:30         ` Tom de Vries
2020-08-28 15:23           ` Pedro Alves
2020-08-28 15:14         ` Pedro Alves
2020-08-28 16:15           ` Tom de Vries

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=23b43acc-9846-a03c-5207-3ae80efc1d6f@palves.net \
    --to=pedro@palves.net \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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