public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "prashant.malladi at amd dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29967] Issue with line number information after symbols read from elf
Date: Wed, 11 Jan 2023 05:57:07 +0000 [thread overview]
Message-ID: <bug-29967-4717-8Xtavj8le3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29967-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29967
--- Comment #3 from Malladi, Prashant <prashant.malladi at amd dot com> ---
Thanks for you comments Tom.
Do you think, the elf generation is fine?
Any problem with these line statements - especially the first 2 lines here.
-------------------------------------------------------------------
Line Number Statements:
[0x0000021b] Extended opcode 2: set Address to 0x0
[0x00000222] Advance Line by -1 to 0
[0x00000224] Set File Name to entry 1 in the File Name Table
[0x00000226] Advance Line by 33 to 33
[0x00000228] Advance PC by 272 to 0x110
[0x0000022b] Copy
[0x0000022c] Set is stmt to 1
[0x0000022d] Special opcode 5: advance Address by 0 to 0x110 and Line by 0 to
33
-------------------------------------------------------------------
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-11 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 11:16 [Bug gdb/29967] New: " prashant.malladi at amd dot com
2023-01-06 11:18 ` [Bug gdb/29967] " prashant.malladi at amd dot com
2023-01-06 19:32 ` tromey at sourceware dot org
2023-01-11 5:57 ` prashant.malladi at amd dot com [this message]
2023-01-11 20:54 ` tromey at sourceware dot org
2023-09-05 11:00 ` rajesh.palla at amd 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-29967-4717-8Xtavj8le3@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).