Date: Sat, 11 Jul 2020 18:51:12 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239516] readelf -wf segfaults on most (all?) debug info files Message-ID: <bug-239516-227-9JVUmZD7sd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239516-227@https.bugs.freebsd.org/bugzilla/> References: <bug-239516-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239516 Mark Johnston <markj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |markj@FreeBSD.org Status|New |In Progress --- Comment #3 from Mark Johnston <markj@FreeBSD.org> --- (In reply to Paco Pascal from comment #2) My apologies for not following up sooner! I think you indeed found the root cause, thanks. Thinking about this some more, I suspect that libdwarf shou= ld be handling this case itself, rather than forcing it into consumers. I looked at SGI libdwarf, and it appears to handle this: dwarf_elf_object_access_load_section() looks for a NULL d_buf in the data descriptor of the target ELF section, which indicates that the section is SHT_NOBITS. I proposed a patch here: https://reviews.freebsd.org/D25626 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239516-227-9JVUmZD7sd>