Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Return argv0-symlink.exp early if gdb can't load symlink
Date: Thu, 10 Apr 2014 13:19:00 -0000	[thread overview]
Message-ID: <534699C8.3040804@codesourcery.com> (raw)
In-Reply-To: <83mwg3brux.fsf@gnu.org>

On 04/03/2014 12:47 AM, Eli Zaretskii wrote:
> What do you mean by "load"?  Which command failed?
> 

Here are the steps to create a symlink and load symlink in GDB.

$ export CYGWIN=winsymlinks:nativestrict
$ ln -sf wchar wchar-filelink
$ file wchar-filelink
wchar-filelink: symbolic link to `wchar'

(gdb) file ~/wchar-filelink
"C:\cygwin\home\yqi/wchar-filelink": not in executable format: File
format not recognized

This error is emitted by

      if (!bfd_check_format_matches (exec_bfd, bfd_object, &matching))
        {
          /* Make sure to close exec_bfd, or else "run" might try to use
             it.  */
          exec_close ();
          error (_("\"%s\": not in executable format: %s"),
                 scratch_pathname,
                 gdb_bfd_errmsg (bfd_get_error (), matching));
        }

I suspect that BFD doesn't recognize native symlink on windows.  I'll
dig into bfd.

-- 
Yao (齐尧)


  reply	other threads:[~2014-04-10 13:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02  8:46 Yao Qi
2014-04-02  8:59 ` Yao Qi
2014-04-02 10:47   ` Pedro Alves
2014-04-02 14:06     ` Yao Qi
2014-04-02 16:44       ` Pedro Alves
2014-04-02 16:47       ` Eli Zaretskii
2014-04-10 13:19         ` Yao Qi [this message]
2014-04-02 16:14   ` Eli Zaretskii
2014-04-02 16:54     ` Pedro Alves
2014-04-02 17:20       ` Eli Zaretskii
2014-04-03 12:12         ` Pedro Alves

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=534699C8.3040804@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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