[PATCH v5] Implement the ability to set/unset environment variables to GDBserver when starting the inferior

Simon Marchi simon.marchi@ericsson.com
Tue Sep 5 16:26:00 GMT 2017


On 2017-09-05 05:32 PM, Thomas Preudhomme wrote:
> Hi Sergio,
> 
> I noticed that the share-env-with-gdbserver.exp test you added is skipped if using a gdb stub. However the comment says the test is meaningless for native-gdbserver. Shouldn't the check also look whether this is a cross debugger?
> 
> Best regards,
> 
> Thomas

Why would a cross debugger make this test irrelevant?  If you are debugging
your ARM board from your x86 PC, you can still set environment variables
for new processes that are spawned by gdbserver.  I have the feeling that
you are confused by the meanings of the various terms (native/remote/
extended-remote/cross/etc), which is understandable because these terms
have different meanings depending on the context.  Can you expand on why
you think this is wrong, and maybe we can find where the possible confusion
comes from?

Simon



More information about the Gdb-patches mailing list