This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Remove comments from user_code in gdb_test_multiple
- From: Andrew STUBBS <andrew dot stubbs at st dot com>
- To: Markus Deuling <deuling at de dot ibm dot com>
- Cc: Daniel Jacobowitz <drow at false dot org>, Ulrich Weigand <uweigand at de dot ibm dot com>, GDB Patches <gdb-patches at sourceware dot org>
- Date: Thu, 27 Mar 2008 16:35:08 +0000
- Subject: Re: [patch] Remove comments from user_code in gdb_test_multiple
- References: <47EBBBFA.4010700@de.ibm.com> <20080327153159.GA8060@caradoc.them.org> <47EBC15C.6070306@de.ibm.com>
Markus Deuling wrote:
What do you think about the spu info mailbox patch then ? Move the
comment above gdb_test_multiple ? Or use send_gdb/gdb_expect and have
the comments in the right place?
The (?#) directive allows you to put the comments inside the regular
expression itself.
-re "(?#Older kernels had a bug that caused them to return arbitrary
values when
attempting to read from an empty mailbox via spufs.
)SPU Outbound Mailbox.*0x.*SPU Outbound Interrupt
Mailbox.*0x.*$gdb_prompt $"
Or, alternatively, the (?x) directive might be cleaner. Note that this
changes the meaning of white space.
-re "(?x)
#Older kernels had a bug that caused them to return arbitrary
values when
#attempting to read from an empty mailbox via spufs.
SPU Outbound Mailbox.*0x.*SPU Outbound Interrupt Mailbox.*0x.*
$gdb_prompt[ ]$"
This is untested!
Andrew