[PATCH] Outwit compiler dead code elimination in break.exp test

Michael Elizabeth Chastain mec.gnu@mindspring.com
Mon Dec 1 16:55:00 GMT 2003


ff> The messages will now be something like:
ff>   PASS: gdb.base/break.exp: set to-be-silent break bp_location1
ff> instead of:
ff>   PASS: gdb.base/break.exp: set to-be-silent break 83

Mmmmm, a test suite discussion.  Can I throw two cents in?  :)

Either message looks fine to me.  It's important that the message
be unique within the test script, and either message would be unique
within the test script.  And it's important that the message not change
from run to run, and "break 83" does not change from run to run
unless someone actually changes the test script.

So "break 83" wasn't a big problem but "break bp_location1" appeals
more to me esthetically.

Michael C



More information about the Gdb-patches mailing list