public inbox for
 help / color / mirror / Atom feed
From: "E, Nagajyothi" <>
To: Mark Wielaard <>,
	"" <>
Cc: "George, Jini Susan" <>,
	"Achra, Nitika" <>,
	"Sharma, Alok Kumar" <>,
	"E, Nagajyothi" <>
Subject: RE: Plan to contribute for supporting split dwarf (-gsplit-dwarf) in dwz
Date: Wed, 17 Feb 2021 05:53:56 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[AMD Official Use Only - Internal Distribution Only]


I am working on adding support for the dwarf5 .debug_str_offsets, .debug_addr sections and the related forms DW_FORM_strx[1234], DW_FORM_addrx[1234].
Please let me know if anyone has already started work on these.


-----Original Message-----
From: Mark Wielaard <> 
Sent: Tuesday, February 16, 2021 12:24 AM
To: Sharma, Alok Kumar <>
Cc:; George, Jini Susan <>; E, Nagajyothi <>; Achra, Nitika <>
Subject: Re: Plan to contribute for supporting split dwarf (-gsplit-dwarf) in dwz

[CAUTION: External Email]

Hi Alok,

On Mon, Feb 15, 2021 at 05:26:29PM +0000, Sharma, Alok Kumar via Dwz wrote:
> I am planning to contribute for supporting split DWARF.
> Please let me know if it is already being worked on?

That is great. Nobody is currently working on that as far as I know. One issue to resolve is knowing how to "unsplit" the DWARF first. Since it isn't clear (to me) whether it makes sense to do split DWARF .dwo (sections/files) together with Supplementary DWARF Object references. One idea might be to handle DWP processed files?

There are a couple of bugs that might be prerequirements for handling split DWARF, you probably need "split" variants of these bugs:;;sdata=HiyzxPs6SJnUE%2BMEKAsUE8HL2dvneJD1V7Yfcb9ZDcQ%3D&amp;reserved=0;;sdata=QpjPErW8i8JG75ke528vxPry5pvkwfIq6QO3yxdxURo%3D&amp;reserved=0;;sdata=h4WU7ejc7KeSBEluEAgnM5%2FRMRTOVMjRXuzZVbdBlec%3D&amp;reserved=0

See also this comment:;;sdata=uLu90OuqGGBKIFwqItGHPNomPHb2HJNG8TkXKJ%2FUggM%3D&amp;reserved=0
Which describes some other issues, like DW_FORM_strx, .debug_str_offset, DW_FORM_rnglistx and various _base attributes that need supporting.
(This should probabably have their own bugs filed.)

There is already one explicit -gsplit-dwarf variant bug:;;sdata=%2BoaV%2Fqfl7feS7siRNIsze0aZui7S9qN17vBj%2FYOkjdA%3D&amp;reserved=0 But that is only for part of the problem (and might be simply resolved by bug #27375).



  reply	other threads:[~2021-02-17  5:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 17:26 Sharma, Alok Kumar
2021-02-15 18:54 ` Mark Wielaard
2021-02-17  5:53   ` E, Nagajyothi [this message]
2021-02-18 14:45     ` Mark Wielaard
2021-02-22  3:39       ` E, Nagajyothi

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).