public inbox for
 help / color / mirror / Atom feed
From: Simon Marchi <>
To: Jan Vrany <>, GDB mailing list <>
Subject: Re: Hand-written assembly and Python API
Date: Fri, 29 Apr 2022 08:54:25 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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/default/
> 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 <returnFromJIT1>
> 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 python
> 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.


  reply	other threads:[~2022-04-29 12:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 12:32 Jan Vrany
2022-04-29 12:54 ` Simon Marchi [this message]
2022-04-29 13:10   ` Jan Vrany

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).