From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1B3B73858D32; Thu, 16 Nov 2023 10:42:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1B3B73858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1700131356; bh=E8b3qkzuh5he3My+ymkrSiLtiWkXCDtbvcC8hYTEfqQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=W+VmcmE95mBEcq8Pck1KfgoKTduVOZadNHa+nDX8oAy9T5odROcc0Ocn5f7FBRgaF RHHuziEsIKSnhPj2ay5ywfzi1067NBDdMMMZ1Dr7eFQYtZq3hImkI923Ksy3PfIAZA LLSnpzMvQ+7tRSzc0rdR9KMy4hrMDCrurkFW1D7o= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/28623] Missing catching return of execve syscall of PowerPC Date: Thu, 16 Nov 2023 10:42:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW 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=3D28623 --- Comment #2 from Tom de Vries --- Using this demonstrator patch I can hit the syscall exit: ... diff --git a/gdb/ppc-linux-tdep.c b/gdb/ppc-linux-tdep.c index 0c676a8..a5cfb7d 100644 --- a/gdb/ppc-linux-tdep.c +++ b/gdb/ppc-linux-tdep.c @@ -1344,6 +1344,8 @@ ppc_gdbarch_tdep *tdep =3D gdbarch_tdep (gdbarch); enum bfd_endian byte_order =3D gdbarch_byte_order (gdbarch); + return 11; + /* Make sure we're in a 32- or 64-bit machine */ gdb_assert (tdep->wordsize =3D=3D 4 || tdep->wordsize =3D=3D 8); ... which allows me to sample the registers: ... (gdb) info registers r0 0x0 0 r1 0x7fffffffee10 140737488350736 r2 0x0 0 r3 0x0 0 r4 0x0 0 r5 0x0 0 r6 0x0 0 r7 0x0 0 r8 0x0 0 r9 0x0 0 r10 0x0 0 r11 0x0 0 r12 0x7ffff7fb19e0 140737353816544 r13 0x0 0 r14 0x0 0 r15 0x0 0 r16 0x0 0 r17 0x0 0 r18 0x0 0 r19 0x0 0 r20 0x0 0 r21 0x0 0 r22 0x0 0 r23 0x0 0 r24 0x0 0 r25 0x0 0 r26 0x0 0 r27 0x0 0 r28 0x0 0 r29 0x0 0 r30 0x0 0 r31 0x0 0 pc 0x7ffff7fb19e0 0x7ffff7fb19e0 <_start> msr 0xb00000000000d033 12682136550675370035 cr 0x0 0 lr 0x0 0x0 ctr 0x0 0 xer 0x0 0 fpscr 0x0 0 vscr 0x0 0 vrsave 0xffffffff -1 ppr 0xc000000000000 3377699720527872 dscr 0x10 16 tar 0x0 0 bescr ebbhr ebbrr mmcr0 0x0 0 mmcr2 0x0 0 siar 0x0 0 sdar 0x0 0 sier 0x0 0 orig_r3 0x7ffffffff1c5 140737488351685 trap 0xc00 3072 ... Looks like the lr =3D=3D 0 approach might work here as well. --=20 You are receiving this mail because: You are on the CC list for the bug.=