Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Peter Steiner <sp@med-2-med.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb darwin target on Linux host?
Date: Wed, 20 Oct 2010 14:42:00 -0000	[thread overview]
Message-ID: <20101020144225.2316031366@nx.neverkill.us> (raw)
In-Reply-To: <20101020143016.6BE9131366@nx.neverkill.us>

On Wed, 2010-10-20 at 16:20 +0200, Tristan Gingold wrote:
> Could you post the log messages ?  I suppose that if no binary is
> built, then an error has occurred.
> 
> Not sure why you try to build such a tool, as it would be basically
> useless to debug.
> 
Hi

found the bug - there must be some typo/bug in your build system as it
does not build the gdb/ directory at all with --target=x86_64-darwin!

I had to run configure in topdir first then after it finishes cd gdb,
then rerun same configure (--target=x86_64-darwin) in gdb dir, make,
cd .. && make install.

This worked and gives me:

l /usr/local/gdb/bin/
total 44032
drwxr-xr-x 2 root root     4096 2010-10-20 16:22 ./
drwxr-xr-x 6 root root     4096 2010-10-20 16:05 ../
-rwxr-xr-x 1 root root 17567402 2010-10-20 16:22
x86_64-apple-darwin-gdb*
-rwxr-xr-x 1 root root 17567431 2010-10-20 16:22
x86_64-apple-darwin-gdbtui*

BUT, there is another issue now. The so generated
x86_64-apple-darwin-gdb* does not recognize 64bit binaries:

(e.g. /home/exchange/ls is the binary I want to debug)

/usr/local/gdb/bin/x86_64-apple-darwin-gdb /home/exchange/ls
 
GNU gdb (GDB) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "--host= --target=x86_64-apple-darwin".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
"/home/exchange/ls": not in executable format: File format not
recognized
Setting up the environment for debugging gdb.

WHY it says:

"/home/exchange/ls": not in executable format: File format not
recognized

?

as I built for the darwin target?

file /home/exchange/ls
/home/exchange/ls: Mach-O fat file with 2 architectures



  parent reply	other threads:[~2010-10-20 14:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 13:53 Peter Steiner
2010-10-20 14:20 ` Tristan Gingold
2010-10-20 14:26   ` Pedro Alves
2010-10-20 14:41     ` Tristan Gingold
2010-10-20 14:50       ` Pedro Alves
2010-10-20 14:52         ` Nathan Froyd
2010-10-20 15:09           ` Pedro Alves
     [not found]           ` <20101020150949.4841131366@nx.neverkill.us>
2010-10-20 15:15             ` Peter Steiner
     [not found] ` <20101020143016.6BE9131366@nx.neverkill.us>
2010-10-20 14:42   ` Peter Steiner [this message]
2010-10-20 15:12     ` Tristan Gingold
     [not found]     ` <20101020151257.25F2D31366@nx.neverkill.us>
2010-10-20 15:24       ` Peter Steiner
2010-10-20 17:12         ` Stan Shebs
2010-10-21  7:49           ` Tristan Gingold
2010-10-20 15:35       ` Peter Steiner
     [not found]       ` <1287588922.28107.281.camel@hp>
2010-10-20 15:45         ` Paul Starzetz

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=20101020144225.2316031366@nx.neverkill.us \
    --to=sp@med-2-med.com \
    --cc=gdb@sourceware.org \
    --cc=gingold@adacore.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