This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [PATCH 05/14] gdb/testsuite: Skip a few gdb.base/skip.exp tests for remote targets


> >
> > This is not what i see with a standard remote gdbserver-based test. For board
> "native-gdbserver" i see all the tests passing just fine.
> >
> > GDB gets fired up and these first few checks get done without connecting to
> gdbserver. Then GDB proceeds to connect to gdbserver.
> >
> > This, again, seems to indicate there is some custom board file in your setup
> that is implementing testsuite primitives (that prepare_for_testing calls)
> differently than what is present in GDB's testsuite.
> >
> > Am i missing something?
> 
> Anton, could you share your experience with us?
> 

I don't remember the details, but if I read that correctly, the fix assumes
that checks are done after connecting to the target. Perhaps the behavior has
changed since the patch has been authored? We do use custom board, but I
don't think it modifies test procedures like prepare_for_testing. It does
however implement board specific open, close, and reboot procs, and for one
server we implement custom gdb_comm_leave proc to ensure that each test is run
with a new GDB instance, because GDB-instance reuse was causing troubles in
some cases: 
https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/blob/arc-releases/dejagnu/nsim-extra.exp#L121

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]