From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id Nz4dFRnba2L8TAMAWB0awg (envelope-from ) for ; Fri, 29 Apr 2022 08:33:29 -0400 Received: by simark.ca (Postfix, from userid 112) id 4BA881E058; Fri, 29 Apr 2022 08:33:29 -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=e6pjYbe0; 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=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.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 33C8E1E00E for ; Fri, 29 Apr 2022 08:33:28 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 3E92C389EC53 for ; Fri, 29 Apr 2022 12:33:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3E92C389EC53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1651235607; bh=MgGybhqZ6tuYMlH+S6NqBi6rT1fPsqFbgFT97sWPZQA=; h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=e6pjYbe0Rlo8FwPjzkT5u5SYKWYUI+AOjZ0p32+umnLKgEb6E2nTIDTmctWyNxB54 JVOpTYABEpLIPyCOwGHO9H0QR8+w/VqqgI0jn/b4Y0xWnDEc9DcDK1ruj2X2KDgROB d2f+vhiq+ltMtH90Dj5cN9khk/bVawmF4IQ4GdVc= Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17]) by sourceware.org (Postfix) with ESMTPS id DACDC3856DC4 for ; Fri, 29 Apr 2022 12:32:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DACDC3856DC4 Date: Fri, 29 Apr 2022 12:32:49 +0000 To: GDB mailing list Subject: Hand-written assembly and Python API Message-ID: <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" 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/defaul= t/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_endp= roc is clearly not enough). Or do I have to roll up sleeves and implement pytho= n API for minimal symbols? Thanks! Jan