Re: [PATCH] Make gdb.server/connect-with-no-symbol-file.exp more robust

[Yao Qi <qiyaoltc at gmail dot com>]

Luis Machado <lgustavo@codesourcery.com> writes:

Hi Luis,

> Investigating further i noticed the test, as is,  may delete the original symbol
> files, causing failures to occur.
>
> I went ahead and adjusted the test so it properly restores the state of the
> files with every iteration and also moved the required commands to functions.
>

I think we shouldn't remove any generated files during the test, so that
the fails can be manually reproduced.  Instead of deleting the file, can't
we start gdb with files of different names?  Say, when $action is
"delete", we can just set binfile to
connect-with-no-symbol-file-nonexist.  When $action is "permission",
copy connect-with-no-symbol-file to
connect-with-no-symbol-file-not_permitted, change its permission, and
set binfile to it.  What do you think?

> Unfortunately i see FAIL's (4) with both stdio-based gdbserver boards because,
> obviously, the launching of gdbserver and issuing of the "target remote"
> command happen at the same time. Thus, no time to delete or make the symbol
> file inacessible.

I don't know much about stdio gdbserver, so have no comment on it.

-- 
Yao (éå)