From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id GFzpFezja2K2TgMAWB0awg (envelope-from ) for ; Fri, 29 Apr 2022 09:11:08 -0400 Received: by simark.ca (Postfix, from userid 112) id 5612A1E058; Fri, 29 Apr 2022 09:11:08 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=yDEhwIGL; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id DC77C1E00E for ; Fri, 29 Apr 2022 09:11:07 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 502CB3949F15 for ; Fri, 29 Apr 2022 13:11:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 502CB3949F15 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1651237867; bh=xzvdySx3BoefyFl7JROtyS16EsLQQ3LTuFrXIgHqjVY=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=yDEhwIGL85maoyjYJnhFX3FrISwvIH6sibAteoOE6W25St8sE27Kdt127vka77Js0 wGjuWwUImgHWy2aRDwIjQLBV+LRq7NkFPEycBsS50p0JIQSV8EV1Yax1zbYh4p/ciD +SZLMacbzofnudkioU4kvF5yuhIJaDjaq5+xwN7k= Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) by sourceware.org (Postfix) with ESMTPS id D0A0A385803E for ; Fri, 29 Apr 2022 13:10:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D0A0A385803E Date: Fri, 29 Apr 2022 13:10:31 +0000 To: Simon Marchi , GDB mailing list Subject: Re: Hand-written assembly and Python API Message-ID: In-Reply-To: References: <5dce3fb2110facb58974d1ee546c43b6db20b6f4.camel@vrany.io> Feedback-ID: 40767693:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Jan Vrany via Gdb Reply-To: Jan Vrany Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" On Fri, 2022-04-29 at 08:54 -0400, Simon Marchi wrote: > On 2022-04-29 08:32, Jan Vrany via Gdb wrote: > > Hi folks, > > > > I'm trying to debug a code that uses a handful of > > hand-written assembly routines. For example, one of > > them looks like (its RISC-V but that does not matter): > > > > .text > > .globl returnFromJIT1 > > .type returnFromJIT1,function > > .align 2 > > returnFromJIT1: > > .cfi_startproc > > sd a0,248(s10) > > sd s11,32(s10) > > li a0, 17 > > li a1, 1 > > j cInterpreterFromJIT > > .cfi_endproc > > .size returnFromJIT1, .-returnFromJIT1 > > > > .text > > .globl ... > > > > GDB clealy knows "something" about the assembly routines, it shows > > the source properly and 'info symbol' works too: > > > > (gdb) info symbol 0x3ff75eca24 > > returnFromJIT1 in section .text of /opt/riscv/sysroot/tmp/jdk/lib/de= fault/libj9jit29.so > > > > The problem is how to figure out I'm in (say) `returnFromJIT1` routine > > using Python API: > > > > (gdb) py print(gdb.block_for_pc(0x3ff75eca24).function) > > None > > > > The only way I can think of is to parse value of `gdb.format_address()`= : > > > > (gdb) py print(gdb.format_address(0x3ff75eca24)) > > 0x3ff75eca24 > > > > which is bit awkward (but doable!). > > > > Question is: is there a better way? I can modify the assembly source > > too if there's some directive that may help GDB (.cfi_startproc / .cfi_= endproc > > is clearly not enough). Or do I have to roll up sleeves and implement p= ython > > API for minimal symbols? > > I was going to say "returnFromJIT1" is a minimal symbol, but you clearly > know that already. There is DWARF debug info for assembly when building > with -g (at least when building with gcc / gas), but it only contains > line statements, which allows GDB to show where you are in the source > file (instead of showing disassembly). You won't be able to look up a > block from that. > > I don't know of a way to do it with the current API, unfortunately. > > Simon Thanks!=C2=A0 I was secretly hoping you might know some trick I'm not aware of... Jan