Getting access to environement variables

    Hello,

    I would like to point-out a possibly missing feature, which is the
possibility of accessing ENV variables in GDB commands.

    Currently, if I want my command scripts to work on a remote target
or another, the only way I've found to parametrize the target/port is to
generate a command file in the calling script, and to include it into
the executed script.

    Something like :

#!/bin/bash
GDBPORT=(GDBPORT:=1234)
echo "target remote localhost:${GDBPORT}" > connect.cmd

    And then in the gdb script
include connect.cmd
...

    Is there a better way, or is it the way it is intended top be done ?

    Else, I wanted to thank/copngratulate everyone who contributed to
GDB for their fantastic work building probably the most powerfull
debugger ever (not the most user friendly, still :) ).

    Best regards,
        Vincent.

-- 

*Vincent Dupaquis*
Software security & Cryptography expert
06 24 58 17 05
/Europarc de Pichaury Bâtiment B8 1330 rue Guillibert Gautier de la
Lauzière 13290 Aix-en-Provence/

www.trusted-objects.com <http://www.trusted-objects.com>