Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Frank Tetzel <s1445051@mail.zih.tu-dresden.de>
To: Tony Simpson <agjasimpson@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: jit interface and jit reader
Date: Tue, 22 Jan 2019 17:33:00 -0000	[thread overview]
Message-ID: <20190122183245.7fa29898@archvm> (raw)
In-Reply-To: <CAKJTP-QQ5MTzQnZeQze3XcDNoKY4kGRPnSpKMu5VgZ_fuQ7=+A@mail.gmail.com>

> I think I ran into the same problem a couple of years ago. I fixed my
> problem here
> https://github.com/tonysimpson/binutils-gdb/commits/jit-interface-fixes.
> 
> I've forgotten the details but I remember I got it working with my
> patch - here is the commit message for
> 3c0e5d45f727d5ef98b681103954820c8fbbd700 Fixes:
>   * Named blocks not appearing as functions - can't break on
> functions;
>   * Pending breakpoints on JIT'd code not being resolved;
>   * GDB goes into an infinit loop with more than one JIT block in a
>      symtab;
>   * Unwinder function not being called.
> 
> Hope this helps. Best Regards,

Hi Tony,

thank you very much. Your patch is still working nearly unchanged. I
just checked for gdb 8.2.1 (dict_create_linear_expandable() takes an
argument now, "language").

Breakpoints are working now, even pending ones. The disassemble command
still does not work. But I haven't checked all the changes you did,
e.g., multiple blocks.

Did you try to upstream your changes?

Best regards,
Frank


  reply	other threads:[~2019-01-22 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 10:50 Frank Tetzel
2019-01-21  2:54 ` How to set the same command for all the breakpoints in gdb? Peng Yu
2019-01-21 13:53 ` jit interface and jit reader Frank Tetzel
2019-01-22 11:21   ` Tony Simpson
2019-01-22 17:33     ` Frank Tetzel [this message]
2019-01-22 17:56       ` Tony Simpson

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20190122183245.7fa29898@archvm \
    --to=s1445051@mail.zih.tu-dresden.de \
    --cc=agjasimpson@gmail.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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