|
From: Philippe W. <phi...@sk...> - 2010-04-13 19:38:29
|
Hello,
In the framework of gdbserver in valgrind, I am looking at automating the tests of a gdb
debugging a valgrind-ified process.
Several options are possible for that:
A use of tcl/expect (this is the standard way with which gdb is tested)
B use of perl/expect. I have experimented with this, and it works quite well.
C a "home made" script hack doing something vaguely similar to A or B.
C does not look that attractive (reinventing the wheel).
B looks more attractive than A (as valgrind tests are already using perl).
However, B implies to have the perl expect module installed (at least on fedora, it is
not installed by default).
Is it ok to add perl expect module as a pre-requisite for the gdb tests ?
On top of this perf/expect modul, I am thinking to add a new
gdbprog:
line to be handled by vg_regtest.
When this line is given, it means that vg_regtest will launch two programs:
* one program is the prog: to be "valgrind-ified"
* the other program will (typically) be a perl expect script which will
debug the first program.
The *.stdout.exp and *.stderr.exp will then verify what the 2nd program has
produced.
Does that approach look ok ?
Thanks in advance for any feedback/advice/...
|