Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.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: Tue, 05 Jul 2011 22:18:00 -0000	[thread overview]
Message-ID: <20110705220239.GZ2407@adacore.com> (raw)
In-Reply-To: <CALoOobNUGG=07Sj9oPHfKu=zbT8tiG482N-U-cd_oZht-NmSMA@mail.gmail.com>

> Another option is to apply a better fix (provided it is deemed safe) ...

Thanks for doing that :)

Your fix certainly looks a lot nicer than Jan's! After careful
reading, I think the patch makes sense, but having never looked
at this code before, it would be better if someone else approved.

Can Doug approve the patch, for instance? The patch is OK for 7.3
if OK for HEAD.

> 2011-07-05  Paul Pluzhnikov  <ppluzhnikov@google.com>
> 
> 	jit.c (jit_breakpoint_re_set_internal): Call jit_inferior_init.

Should we say that you're also adding jit_inferior_init's declaration?

Note that some of us (myself included) prefer moving functions
rather than having to write a declaration which duplicates the
amount of work to do when the function profile changes.  But
others disagree, and would rather use these declarations to allow
them to order the functions in a certain order of their liking...
I think that for the 7.3 branch we'll definitely want your version,
to keep the patch as small and simple as possible, but you're free
to choose whichever style you might prefer.

> testsuite/ChangeLog:
> 
> 2011-07-05  Paul Pluzhnikov  <ppluzhnikov@google.com>
> 
> 	* gdb.base/jit-so.exp: New test.
> 	* gdb.base/jit-dlmain.c: New file.
> 	* gdb.base/jit-main.c: Allow "main" to be elsewhere.

Cheers,
-- 
Joel


  reply	other threads:[~2011-07-05 22:03 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 [this message]
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

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=20110705220239.GZ2407@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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