public inbox for
 help / color / mirror / Atom feed
From: Jan Vrany <>
To: Ludvig Janiuk <>,
	"" <>
Subject: Re: Error in docs, " Writing a Frame Filter" + question
Date: Fri, 13 May 2022 11:48:47 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, 2022-05-13 at 09:33 +0000, Ludvig Janiuk via Gdb wrote:
> Hi,
> I'd like to report an error in the page " Writing a Frame Filter" at
> One of the code listings mentions "ElidingFrameDecorator", however this class is never defined. I believe "ElidingInlineDecorator" was intended.
> While I'm at it, I'd also like to ask a question on the Python API. I have a script which unwinds and filters Java Virtual Machine frames, and it seems to
> work well in backtraces (gdb command "bt"). However, when I want to look closer on one of the frames (gdb command "frame <X>"), I get something like "#5
> 0x00007fffd96f923e in ?? ()" again. Does the Python frame unwinding API only apply to the backtrace command, or is there something I can do to make my Java
> frames visible also in the output of other commands?

You can implement FrameDecorator that would provide proper (method) name for given frame
(and even source and line number, local variables - see FrameDecorator API).

This helps, but still, other GDB commands won't know anything about JITed code so
you cannot easily set breakpoints or disassembly them. AFAIK, there's no Python
API for that. I'm doing some experiments towards having that (see my other email [1]),
but it is still very much WIP.

HTH, Jan


> Best regards,
> //Ludvig Janiuk
> Oracle

      reply	other threads:[~2022-05-13 11:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13  9:33 Ludvig Janiuk
2022-05-13 11:48 ` Jan Vrany [this message]

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).