This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [ob] Eliminate another gdb_suppress_entire_file
> I've been using untested followed by return. Why wouldn't that be
> ideal?
It's actually pretty good. I think in some cases unsupported might
be a better choice, but I like untested too, because it's always
going to be true...
I see in your patch that you used the name of the .exp file as
the argument of untested. Should we do that, or should we try
to preserve the string we previously used with gdb_suppress_entire_file?
--
Joel