Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] new test for separate debug info
Date: Fri, 14 Nov 2003 14:30:00 -0000	[thread overview]
Message-ID: <16308.59112.465627.523785@localhost.redhat.com> (raw)
In-Reply-To: <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
 >   }
 > 


  reply	other threads:[~2003-11-14 14:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14  5:14 Michael Elizabeth Chastain
2003-11-14 14:30 ` Elena Zannoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-14  2:47 Michael Elizabeth Chastain
2004-01-14 15:09 ` Elena Zannoni
2004-01-13 22:24 Michael Elizabeth Chastain
2004-01-13 23:37 ` Elena Zannoni
2004-01-13  5:19 Michael Elizabeth Chastain
2004-01-13 17:18 ` Elena Zannoni
2004-01-13  2:28 Michael Elizabeth Chastain
2004-01-13  4:49 ` Elena Zannoni
2003-11-14 19:37 Michael Elizabeth Chastain
2003-11-14 20:09 ` Elena Zannoni
2004-01-12 17:20   ` Elena Zannoni
2004-01-12 22:01     ` Andrew Cagney
2004-01-12 22:28       ` Daniel Jacobowitz
2004-01-12 23:11         ` Elena Zannoni
2004-01-12 23:20           ` Daniel Jacobowitz
2004-01-13  3:12           ` Ian Lance Taylor
2004-01-16 19:55         ` Andrew Cagney
2004-01-16 22:41           ` Daniel Jacobowitz
2003-11-14 15:18 Michael Elizabeth Chastain
2003-11-14 15:52 ` Elena Zannoni
2003-11-14  4:57 Michael Elizabeth Chastain
2003-11-14 14:32 ` Elena Zannoni
2003-11-13 17:55 Michael Elizabeth Chastain
2003-11-13 19:23 ` Elena Zannoni
2003-11-13 20:08 ` Elena Zannoni
2003-11-13 23:15 ` Elena Zannoni
2003-11-14  4:22   ` Daniel Jacobowitz
2003-11-14 14:34     ` Elena Zannoni
2003-11-13 16:49 Michael Elizabeth Chastain
2003-11-12 22:13 Elena Zannoni
2003-11-12 22:29 ` Daniel Jacobowitz
2003-11-13 16:18   ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16308.59112.465627.523785@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox