From: Tristan Gingold <gingold@adacore.com>
To: Peter Steiner <sp@med-2-med.com>
Cc: gdb@sourceware.org
Subject: Re: gdb darwin target on Linux host?
Date: Wed, 20 Oct 2010 15:12:00 -0000 [thread overview]
Message-ID: <B5283D7D-5BAC-4A01-8904-5D7B6062F9A9@adacore.com> (raw)
In-Reply-To: <20101020144225.2316031366@nx.neverkill.us>
On Oct 20, 2010, at 4:42 PM, Peter Steiner wrote:
> 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.
> "/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
You can't debug fat binaries. You have to extract the executable you really want to debug.
next prev parent reply other threads:[~2010-10-20 15:12 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
2010-10-20 15:12 ` Tristan Gingold [this message]
[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=B5283D7D-5BAC-4A01-8904-5D7B6062F9A9@adacore.com \
--to=gingold@adacore.com \
--cc=gdb@sourceware.org \
--cc=sp@med-2-med.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