Re: [RFA] new test for separate debug info

Michael Elizabeth Chastain
2003-11-14T15:18:02Z

eza> What happens is that gdb_load errors out and calls perror, then
eza> returns 1. All I have done is wrap gdb_load in a check for a 1 return
eza> value.

Here's the part that's confusing me. Your gdb_load wrapper
says "if [gdb_load ...] { unsupported ...}", but your gdb.sum
file says "# of unresolved test cases: 1". The call to "unsupported"
doesn't fit the result of "unresolved"!

eza> The alternative is to alter the gdb_load (or whatever gets
eza> caled from it) to recognize that error and do something specific, but
eza> I thought that was too ad hoc a behavior for a generic procedure.

Ah, okay.

Michael C