public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Jaydeep Chauhan via Gdb <gdb@sourceware.org>
Subject: Re: Line number zero in line table gives incorrect debugging experince with gdb
Date: Fri, 28 Aug 2020 10:59:39 -0600	[thread overview]
Message-ID: <87h7sm905g.fsf@tromey.com> (raw)
In-Reply-To: <CAMyYBzyy-RJn5L210fgyktPNxn4We6bvR+_AxNzxpbmNFTWJbA@mail.gmail.com> (Jaydeep Chauhan via Gdb's message of "Thu, 27 Aug 2020 20:32:56 +0530")

>>>>> "Jaydeep" == Jaydeep Chauhan via Gdb <gdb@sourceware.org> writes:

Jaydeep> We have a situation with GDB(latest trunk)  and  below testcase
Jaydeep> referred for further discussion :

I tried git master gdb today on the gdb.o you sent, and I see a
different result.  I can't run the program in question, but setting a
breakpoint seemed to work:

(gdb) b main
Breakpoint 1 at 0x1c: file gdb.c, line 5.

I somewhat expected this, because some fixes here have landed, in
particular:

    commit 876518dd0a0b6fd6f4ad0a0b247db0d6a267db27
    Author: Tom de Vries <tdevries@suse.de>
    Date:   Sat Jul 25 00:23:06 2020 +0200

        [gdb/symtab] Ignore zero line table entries

Does your tree include this commit?

If so, then I wonder why I see something different.  If not, could you
update to (at least) this revision and then try again?  Maybe it's been
fixed.

Tom

  reply	other threads:[~2020-08-28 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMyYBzxgL3NG++gO_Z2AhZXfSTagd6YBAMd=Ej1TbtitAayX3g@mail.gmail.com>
     [not found] ` <CAMyYBzwV9dr5Aue-rrrbtLRc30F==OaVih91kpzF8KpBtaqMNQ@mail.gmail.com>
2020-08-27 15:02   ` [gdb]Line " Jaydeep Chauhan
2020-08-28 16:59     ` Tom Tromey [this message]
2020-08-28 18:03       ` Line " Simon Marchi

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=87h7sm905g.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb@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).