From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CF4473858027; Wed, 28 Sep 2022 09:45:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CF4473858027 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1664358344; bh=5OkKWot2Qh9AapWtRzDfKKb0QLIU37teXtr+K6VyUyA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=j6TGFtc1Oe1/Ny3b8im4r4j0yee9uj6n0LXj4/Ik3ka1/q6YU8oyW1WkpRgFSnMsC QoAxrxDfaJ40dtKaUZr/RELII1dmP9Hh1xJSrVwWAVKOy/p+BTtMOleEo0qHh8fRKH q2NS9oLxL/S/5pT9C3arn2kKefLlX6swHW9RUkUM= From: "dluyaning at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/29622] Open file permission error under aarch64 architecture Date: Wed, 28 Sep 2022 09:45:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.28 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dluyaning at gmail dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org 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=3D29622 --- Comment #2 from YaNing Lu --- (In reply to Andreas Schwab from comment #1) > 2.28 =E4=B8=8D=E5=86=8D=E5=8F=97=E6=94=AF=E6=8C=81=EF=BC=8C=E6=88=91=E6= =97=A0=E6=B3=95=E7=94=A8 2.36 =E9=87=8D=E7=8E=B0=E5=AE=83=E3=80=82 __libc_openat64 There seems to be no change from 2.28 to 2.36. Can you prov= ide a debugging method for debugging glibc 2.36? --=20 You are receiving this mail because: You are on the CC list for the bug.=