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] |
Several gdb tests get multiple ERRORS and/or timeouts for some multilibs of some embedded targets, with a few tests timing out a dozen times. I would like to modify these tests to look for the first expected ERROR or timeout and then bail out with an indication that the remainder of the test has been skipped. I haven't found a standard way to do this; any suggestions? I've attached a couple of examples as a starting point for discussion. Janis Johnson CodeSourcery / Mentor Graphics
Attachment:
gdb-20110504-2
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |