Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: brobecker@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: Problems with dejagnu and c++ tests...
Date: Wed, 04 Feb 2004 12:50:00 -0000	[thread overview]
Message-ID: <20040204125005.53EB84B364@berman.michael-chastain.com> (raw)

Joel Brobecker reports

  <<
  Running ./gdb.cp/ambiguous.exp ...
  ERROR: (DejaGnu) proc "default_target_compile: Can't find g++." does not exist.
  The error code is NONE
  The info on the error is:
  close: invalid spawn id (6)
      while executing
  "close -i 6"
      invoked from within
  "catch "close -i $spawn_id""
  >>

Rats, this is my clever code in get_compiler_info blowing up.

ambiguous.exp calls get_compiler_info.  get_compiler_info calls
gdb_compile, captures the output, and eval's the output.

That explains the weird message about "proc" not found.

What was the previous behavior when you did not have a C++ compiler?

Michael C


             reply	other threads:[~2004-02-04 12:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04 12:50 Michael Elizabeth Chastain [this message]
2004-02-04 13:20 ` Joel Brobecker
  -- strict thread matches above, loose matches on Subject: below --
2004-02-04 23:50 Michael Elizabeth Chastain
2004-02-04 23:55 ` Daniel Jacobowitz
2004-02-04 23:03 Michael Elizabeth Chastain
2004-02-04 23:13 ` Daniel Jacobowitz
2004-02-04 22:31 Michael Elizabeth Chastain
2004-02-04 22:49 ` Andrew Cagney
2004-02-04 14:01 Michael Elizabeth Chastain
2004-02-04 15:41 ` Andrew Cagney
2004-02-04 11:58 Joel Brobecker

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=20040204125005.53EB84B364@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.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