This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] new test for separate debug info
- From: Elena Zannoni <ezannoni at redhat dot com>
- To: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- Cc: ezannoni at redhat dot com, gdb-patches at sources dot redhat dot com
- Date: Fri, 14 Nov 2003 09:30:00 -0500
- Subject: Re: [RFA] new test for separate debug info
- References: <20031114051503.8BDDB4B3FA@berman.michael-chastain.com>
Michael Elizabeth Chastain writes:
> Woah, I am confused.
>
> Your source code says "unsupported", but your gdb.sum file says
> "unresolved", and your gdb.log file says "ERROR".
>
> Is your sandbox a little messed up, or is it me?!
>
What happens is that gdb_load errors out and calls perror, then
returns 1. All I have done is wrap gdb_load in a check for a 1 return
value. The alternative is to alter the gdb_load (or whatever gets
caled from it) to recognize that error and do something specific, but
I thought that was too ad hoc a behavior for a generic procedure.
elena
> Michael C
>
> ===
>
> ok, How about this behavior?
>
> Running /to/scratch/ezannoni/pristine/src/gdb/testsuite/gdb.base/sepdebug.exp ...
> ERROR: couldn't load /to/scratch/ezannoni/pristine/tomago/gdb/testsuite/gdb.base/sepdebug.dbglnk into /to/scratch/ezannoni/pristine/tomago/gdb/testsuite/../../gdb/gdb.
>
> === gdb Summary ===
>
> # of unresolved testcases 1
> /to/scratch/ezannoni/pristine/tomago/gdb/testsuite/../../gdb/gdb version 2003-11-07-cvs -nx
>
>
> I added a wrapper around the gdb_load call:
>
> if [gdb_load ${binfile}] {
> unsupported "Gdb cannot process a separate debug info file"
> return -1
> }
>