From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29347] abipkgdiff SEGV's on apptainer.
Date: Sat, 09 Jul 2022 21:48:14 +0000 [thread overview]
Message-ID: <bug-29347-9487-2Mc0JPRmMI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29347-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29347
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Ben Woodard from comment #1)
> It appears like exactly the same thing happens with containerd
>
> $ abipkgdiff --self-check --d1
> /home/ben/.cache/fedabipkgdiff/downloads/containerd-debuginfo-1.6.6-4.fc36.
> x86_64.rpm
> /home/ben/.cache/fedabipkgdiff/downloads/containerd-1.6.6-4.fc36.x86_64.rpm
>
>
> Thread 4 "abipkgdiff" received signal SIGSEGV, Segmentation fault.
It is a this cyclic definition in
/usr/lib/debug/usr/bin/containerd-stress-1.6.6-4.fc36.x86_64.debug
[112f71] subroutine_type abbrev: 48
name (string) "text/template/parse.stateFn"
byte_size (udata) 8
lo_user+0x900 (data1) 19
lo_user+0x904 (addr) +0x00000000000bf820
[112f98] formal_parameter abbrev: 17
type (ref_addr) [112dff]
[112f9d] formal_parameter abbrev: 17
type (ref_addr) [112fc4]
[112fa3] typedef abbrev: 47
name (string) "text/template/parse.stateFn"
type (ref_addr) [112f71]
[112fc4] pointer_type abbrev: 50
name (string) "*text/template/parse.stateFn"
type (ref_addr) [112fa3]
lo_user+0x900 (data1) 0
lo_user+0x904 (addr) +0x0000000000057cc0
So the subroutine has one argument which is a pointer to a typedef for the
subroutine itself.
This causes a stack overflow in die_pretty_print_type trying to create a string
representation for that subroutine.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-09 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 19:32 [Bug default/29347] New: " woodard at redhat dot com
2022-07-09 20:40 ` [Bug default/29347] " woodard at redhat dot com
2022-07-09 21:48 ` mark at klomp dot org [this message]
2022-07-28 21:56 ` woodard at redhat dot com
2022-07-28 21:58 ` woodard at redhat 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-29347-9487-2Mc0JPRmMI@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@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).