[PATCH v3 1/3] gdb: call post_create_inferior at end of follow_fork_inferior

Simon Marchi simon.marchi@polymtl.ca
Thu Jul 15 03:20:39 GMT 2021



On 2021-07-02 1:54 p.m., Pedro Alves wrote:
> On 2021-06-10 3:33 p.m., Simon Marchi via Gdb-patches wrote:
>> GDB doesn't handle well the case of an inferior using the JIT interface
>> to register JIT-ed objiles and forking.  If an inferior registers a code
> 
> typo: objiles -> objfiles
> 
>> There isn't currently a way to get visibility into GDB's idea of the JIT
>> code objects for each inferior.  For the purpose of this test, add the
>> "maintenance info jit" command.  There isn't much we can print about the
>> JIT code objects except their load address.  So the output looks a bit
>> bare, but it's good enough for the test.
> 
> The patch looks good to me.  I was just a little surprised with the output
> of the "maintenance info jit" command.  Specificially, the "-" looked odd to
> me, because it looks like either an incomplete range (like start-end), or
> a minus/negative sign.
> 
>  (gdb) maint info jit
>  Base address of known JIT-ed objfiles:
>   - 0x5555555596b0
> 
> I would just drop the "-".  But it's really no biggie and I'm fine with
> leaving it.
> 
> Pedro Alves
> 

I fixed both and pushed this patch, thanks.

Simon


More information about the Gdb-patches mailing list