From: Matthias Klose <doko@ubuntu.com>
To: Denis Khalikov <d.khalikov@partner.samsung.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][PR sanitizer/77631] Support separate debug info in libbacktrace
Date: Sun, 18 Jun 2017 14:09:00 -0000 [thread overview]
Message-ID: <ff60f262-21b2-a16e-d051-e13440aad04b@ubuntu.com> (raw)
In-Reply-To: <2b505c8c-a836-6079-f744-3e9f8acf9356@partner.samsung.com>
On 16.06.2017 17:39, Denis Khalikov wrote:
> Hello everyone,
>
> This is a patch for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77631
>
> Can some one please review attached patch.
not a full review, but it looks like the system debug files based on build-id's
are not found. In newer distro releases you find these at
$ ls /usr/lib/debug/.build-id/
00/ 0d/ 1a/ 25/ 2e/ 3a/ 45/ 4d/ 57/ 64/ 6d/ 77/ 82/ 8b/ 94/ a0/ a9/ b7/ c1/ cd/
d6/ e0/ eb/ f6/
01/ 0e/ 1b/ 26/ 2f/ 3b/ 46/ 4e/ 58/ 65/ 6e/ 78/ 83/ 8c/ 95/ a1/ ac/ b9/ c4/ ce/
d7/ e1/ ec/ f7/
02/ 11/ 1c/ 27/ 30/ 3d/ 47/ 50/ 59/ 66/ 6f/ 79/ 84/ 8e/ 96/ a2/ ae/ ba/ c5/ d0/
d8/ e3/ ee/ f9/
03/ 15/ 1d/ 28/ 32/ 3e/ 48/ 51/ 5b/ 67/ 70/ 7a/ 85/ 8f/ 99/ a3/ b0/ bb/ c6/ d1/
d9/ e4/ ef/ fb/
05/ 16/ 1e/ 29/ 35/ 41/ 49/ 52/ 5c/ 68/ 72/ 7b/ 87/ 90/ 9a/ a4/ b1/ bc/ c8/ d2/
db/ e5/ f1/ fc/
08/ 17/ 1f/ 2a/ 36/ 42/ 4a/ 53/ 5e/ 69/ 73/ 7c/ 88/ 91/ 9b/ a5/ b2/ be/ c9/ d3/
dc/ e6/ f2/ fd/
09/ 18/ 20/ 2b/ 37/ 43/ 4b/ 54/ 60/ 6a/ 75/ 7f/ 89/ 92/ 9c/ a6/ b4/ bf/ cb/ d4/
dd/ e7/ f3/ fe/
0a/ 19/ 24/ 2d/ 39/ 44/ 4c/ 55/ 61/ 6b/ 76/ 80/ 8a/ 93/ 9f/ a7/ b5/ c0/ cc/ d5/
de/ e8/ f5/ ff/
the first two bytes of the crc make the sub dir name, the debug file name has
these first two bytes omitted.
$ ls /usr/lib/debug/.build-id/0d
c55467dc9eb81a00c7715a790844e7cf035345.debug
objdump/objcopy in binutils 2.28 has these lookups properly working.
Matthias
next prev parent reply other threads:[~2017-06-18 14:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170616153942eucas1p1945271f893265484bbb3991a368bcd92@eucas1p1.samsung.com>
2017-06-16 15:39 ` Denis Khalikov
2017-06-18 14:09 ` Matthias Klose [this message]
2017-06-19 8:48 ` Denis Khalikov
2017-06-28 23:59 ` Ian Lance Taylor via gcc-patches
2017-07-01 21:38 ` Denis Khalikov
2017-07-29 20:42 ` Denis Khalikov
2017-09-10 21:11 ` Ian Lance Taylor via gcc-patches
2017-09-11 10:06 ` Denis Khalikov
2017-09-12 14:06 ` Ian Lance Taylor via gcc-patches
2017-09-20 8:54 ` Maxim Ostapenko
2017-09-20 12:33 ` Ian Lance Taylor via gcc-patches
2017-09-20 21:09 ` Ian Lance Taylor via gcc-patches
2017-10-02 11:12 ` Martin Liška
2017-10-02 11:32 ` Jakub Jelinek
2017-10-02 14:01 ` Jakub Jelinek
[not found] <CGME20170313171637eucas1p2d70c4ed7cbd6d088c8c58dc76e1ef722@eucas1p2.samsung.com>
2017-03-13 17:16 ` Denis Khalikov
2017-03-14 8:27 ` Richard Biener
2017-03-14 9:22 ` Matthias Klose
2017-03-14 10:21 ` Denis Khalikov
2017-03-14 13:21 ` Ian Lance Taylor via gcc-patches
2017-03-14 13:46 ` Denis Khalikov
2017-03-14 13:49 ` Ian Lance Taylor via gcc-patches
2017-03-14 14:30 ` Denis Khalikov
2017-03-14 16:26 ` Ian Lance Taylor via gcc-patches
2017-03-14 17:44 ` Denis Khalikov
2017-03-22 15:29 ` Denis Khalikov
2017-04-12 22:08 ` Jeff Law
2017-05-18 14:23 ` Denis Khalikov
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=ff60f262-21b2-a16e-d051-e13440aad04b@ubuntu.com \
--to=doko@ubuntu.com \
--cc=d.khalikov@partner.samsung.com \
--cc=gcc-patches@gcc.gnu.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).