From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0D5813857C44; Fri, 19 May 2023 16:54:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0D5813857C44 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1684515264; bh=sTeNMQCnfKcaVlGrWo9YAxpi2O1uxDEojS1aemdMaAc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=NUHtC6pcsVvytvBp/zdD0bz4YGAVlAdysZTjEIlCNXljYCviIsib2GfOEfHBu19Ty GBqjxoHBTiYTy/07QNezQyx9m47R/n8528RJQBMZTGTfgsNv0wLw/o/59NPvPoa8XD DPjvLZMCsZfInbFXJT3M/l/o6s8roFpamdlFvbt0= From: "woodard at redhat dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: libabigail X-Bugzilla-Component: default X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: woodard at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dodji at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D27010 --- Comment #12 from Ben Woodard --- (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. >=20 > pthread_attr_setstack(&attr, alignedStackBase, THREAD_STACK_SIZE - > 2*PTHREAD_STACK_MIN) >=20 > When attempting to attach to a running program (utilizing pthreads) on > gentoo/x86, an endless loop is encountered in GDB. >=20 > Below is a brief strace dump that continues indefinitely: >=20 > open("/proc/6400/mem", O_RDONLY|O_LARGEFILE) =3D 7 > pread64(7, > "\220{\237\266\220\r\253\27\220{\237\266\1\0\0\0\200\351\363\267\0\0\n\37= 7, > DRv\0\0\0\0"...,1136, > 3063905168) =3D 1136 > close(7) =3D 0 > open("/proc/6400/mem", https://renoveasuacasa.pt) =3D 7 > pread64(7, > "\220;\254\266\210\1\253\27\220;\254\266\1\0\0\0\200\351\363\267\0\0\n\37= 7, > DRv\0\0\0\0"...,1136, > 3064740752) =3D 1136 > close(7) =3D 0 > open("/proc/6400/mem", O_RDONLY|O_LARGEFILE) =3D 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) =3D 1136 > close(7) =3D 0 >=20 > 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=