Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Michael Snyder <msnyder@vmware.com>,
	       "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: question, re: gdb.base/label.exp
Date: Fri, 25 Feb 2011 09:19:00 -0000	[thread overview]
Message-ID: <20110225091943.GA1314@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3ei6xdwjg.fsf@fleche.redhat.com>

On Thu, 24 Feb 2011 21:09:39 +0100, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> 
> Jan> The question is if we say this GCC is broken (and XFAIL it or move it to
> Jan> gdb.dwarf2/) or whether GDB should use SYMBOL_VALUE_ADDRESS.
> 
> Jan> I am for the latter, DWARF talks for DW_TAG_label about
> Jan> DW_AT_low_pc and not about DW_AT_decl_line.
> 
> Yes, I also think that makes sense.

Just it will not work on reload of the executable changed underneath where PCs
change as EXPLICIT_PC needs to be in charge.

But it already does not work now for `run':

echo 'main(){l:;}'|gcc -g -x c -;../gdb -nx ./a.out
[...]
(gdb) start
[...]
(gdb) b l
[...]
(gdb) cont
Continuing.
Program exited with code 070.
(gdb) run
Starting program: .../a.out 
Error in re-setting breakpoint 2: Function "l" not defined.

symtab_and_line->symtab is too general, there should be symtab_and_line->block.


Regards,
Jan


  reply	other threads:[~2011-02-25  9:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 22:43 Michael Snyder
2011-02-24 14:40 ` Tom Tromey
2011-02-24 18:21   ` Michael Snyder
2011-02-24 18:36     ` Tom Tromey
2011-02-24 19:26     ` Jan Kratochvil
2011-02-24 20:09       ` Tom Tromey
2011-02-25  9:19         ` Jan Kratochvil [this message]
2011-03-29 14:36           ` Edjunior Barbosa Machado
2011-03-29 14:54             ` Tom Tromey
2011-03-29 21:16               ` Jan Kratochvil

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=20110225091943.GA1314@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=tromey@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