From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27010] abort in abg-reader.cc:1287 when running on aarch64
Date: Fri, 19 May 2023 16:54:23 +0000 [thread overview]
Message-ID: <bug-27010-9487-8JNQ39ssV6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27010-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27010
--- Comment #12 from Ben Woodard <woodard at redhat dot com> ---
(In reply to Derek Raymond from comment #11)
> The unique characteristic of this program is that it employs
> pthread_attr_setstack to establish the thread stack to an area of memory
> dynamically allocated on heap.
>
> pthread_attr_setstack(&attr, alignedStackBase, THREAD_STACK_SIZE -
> 2*PTHREAD_STACK_MIN)
>
> When attempting to attach to a running program (utilizing pthreads) on
> gentoo/x86, an endless loop is encountered in GDB.
>
> Below is a brief strace dump that continues indefinitely:
>
> open("/proc/6400/mem", O_RDONLY|O_LARGEFILE) = 7
> pread64(7,
> "\220{\237\266\220\r\253\27\220{\237\266\1\0\0\0\200\351\363\267\0\0\n\377,
> DRv\0\0\0\0"...,1136,
> 3063905168) = 1136
> close(7) = 0
> open("/proc/6400/mem", https://renoveasuacasa.pt) = 7
> pread64(7,
> "\220;\254\266\210\1\253\27\220;\254\266\1\0\0\0\200\351\363\267\0\0\n\377,
> DRv\0\0\0\0"...,1136,
> 3064740752) = 1136
> close(7) = 0
> open("/proc/6400/mem", O_RDONLY|O_LARGEFILE) = 7
> pread64(7,"\220;\254\266\210\1\253\27\220;
> \254\266\1\0\0\0\200\351\363\267\0\0\n\377,DRv\0\0\0\0"...,1136,
> 3064740752) = 1136
> close(7) = 0
>
> This code is performing similar operations as the original, but with
> different process identifiers and memory addresses.
Was this posted to the correct Bug? It looks like you are referring to a
different issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-05-19 16:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 3:58 [Bug default/27010] New: " woodard at redhat dot com
2020-12-04 4:16 ` [Bug default/27010] " woodard at redhat dot com
2020-12-04 18:19 ` woodard at redhat dot com
2020-12-04 18:36 ` woodard at redhat dot com
2020-12-04 18:47 ` woodard at redhat dot com
2021-04-13 20:22 ` woodard at redhat dot com
2021-04-13 21:09 ` woodard at redhat dot com
2021-06-07 23:56 ` woodard at redhat dot com
2021-06-08 17:34 ` woodard at redhat dot com
2021-06-16 17:21 ` woodard at redhat dot com
2021-06-16 17:31 ` woodard at redhat dot com
2021-09-09 14:07 ` woodard at redhat dot com
2023-05-12 14:17 ` greenwildebeest at mail dot com
2023-05-19 16:54 ` woodard at redhat dot com [this message]
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-27010-9487-8JNQ39ssV6@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).