On Tue, Jul 5, 2011 at 10:07 AM, Joel Brobecker <brobecker@adacore.com> wrote:

> We're getting ready to produce the first gdb-7.3 candidate release,
> and we're thinking of either:
>  - going with Jan's patch for now, with a view of possibly
>    making it better with a followup patch if necessary;
>  - releasing 7.3 with JIT as a known problem, hopefully to be
>    fixed for 7.3.1, depending on how safe the fix is perceived.

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

Certainly it's ok with me if you decide to go with Jan's patch for now.

It took me  much longer to create a test case (I don't have 'lli'), then
it did to fix the problem once I had the repro.

Thanks,
-- 
Paul Pluzhnikov


2011-07-05  Paul Pluzhnikov  <ppluzhnikov@google.com>

	jit.c (jit_breakpoint_re_set_internal): Call jit_inferior_init.


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.