From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org, Yuri <yuri@rawbw.com>,
Tom Tromey <tromey@redhat.com>
Subject: Re: [patch,7.3] Fix JIT clang-lli gdb-7.3 regression Re: [gdb-7.3] Error in gdb-llvm integration: Unable to read JIT descriptor from remote memory!
Date: Thu, 07 Jul 2011 12:10:00 -0000 [thread overview]
Message-ID: <20110707113444.GA4891@host1.jankratochvil.net> (raw)
In-Reply-To: <CALoOobN=-uRmJCasF8j1iV0npgoVrfMmz6qfoYLNj3_Vn0dHEw@mail.gmail.com>
On Thu, 07 Jul 2011 00:43:50 +0200, Paul Pluzhnikov wrote:
> This then leaves the "unload/reload" case not handled.
What I was trying to exploit with the countercases is that breakpoint_re_set
is designed so that if anything in the inferior changes everything gets
re-set.
Since the former Paul's change 739571cc3151651f49f7171cfd98275d983bfaaa some
information is kept even across breakpoint_re_set which I find against the
design of breakpoint_re_set. It now keeps information about inferior even if
some unspecific inferior change has happened.
The problem is breakpoint_re_set is no longer performance sufficient. This is
a part of the large task Gary Benson is working on, to make inferior solib
notififications local and specific to each solib. But it needs to pass more
information what has changed than the global breakpoint_re_set event. I do
not think that workarounding breakpoint_re_set problems at its callees is
right. But I do not have any further counter testcases.
Thanks,
Jan
prev parent reply other threads:[~2011-07-07 11:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E0FAB8D.2070709@rawbw.com>
2011-07-04 22:21 ` Jan Kratochvil
2011-07-05 2:26 ` Paul Pluzhnikov
2011-07-05 8:00 ` [patch,7.3] Fix JIT clang-lli gdb-7.3 regression Jan Kratochvil
2011-07-05 17:08 ` [patch,7.3] Fix JIT clang-lli gdb-7.3 regression Re: [gdb-7.3] Error in gdb-llvm integration: Unable to read JIT descriptor from remote memory! Tom Tromey
2011-07-05 17:44 ` Joel Brobecker
2011-07-05 21:08 ` Paul Pluzhnikov
2011-07-05 22:18 ` Joel Brobecker
2011-07-05 22:23 ` Paul Pluzhnikov
2011-07-06 12:10 ` [patch,7.3] Fix JIT clang-lli gdb-7.3 regression Jan Kratochvil
2011-07-06 16:12 ` Joel Brobecker
2011-07-06 16:35 ` Paul Pluzhnikov
2011-07-06 16:37 ` Jan Kratochvil
2011-07-06 17:12 ` Paul Pluzhnikov
2011-07-06 17:26 ` Jan Kratochvil
2011-07-06 17:04 ` [patch,7.3] Fix JIT clang-lli gdb-7.3 regression Re: [gdb-7.3] Error in gdb-llvm integration: Unable to read JIT descriptor from remote memory! Paul Pluzhnikov
2011-07-06 22:18 ` Joel Brobecker
2011-07-06 22:50 ` Paul Pluzhnikov
2011-07-06 22:52 ` Joel Brobecker
2011-07-07 12:10 ` Jan Kratochvil [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:
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=20110707113444.GA4891@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.com \
--cc=tromey@redhat.com \
--cc=yuri@rawbw.com \
/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