public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "gingold at adacore dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13901] no handler for the OS ABI "Darwin" when gdb 7.4 built as i386-apple-darwin10.8.0
Date: Mon, 02 Apr 2012 14:41:00 -0000	[thread overview]
Message-ID: <bug-13901-4717-rDyLOvCOQ7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13901-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13901

--- Comment #8 from gingold at adacore dot com <gingold at adacore dot com> 2012-04-02 14:40:56 UTC ---
On Apr 2, 2012, at 4:34 PM, howarth at bromo dot med.uc.edu wrote:

> http://sourceware.org/bugzilla/show_bug.cgi?id=13901
> 
> --- Comment #7 from Jack Howarth <howarth at bromo dot med.uc.edu> 2012-04-02 14:34:09 UTC ---
> On Mon, Apr 02, 2012 at 01:57:55PM +0000, gingold at adacore dot com wrote:
>> http://sourceware.org/bugzilla/show_bug.cgi?id=13901
>> 
>> --- Comment #6 from gingold at adacore dot com <gingold at adacore dot com> 2012-04-02 13:57:55 UTC ---
>> On Apr 2, 2012, at 3:50 PM, howarth at bromo dot med.uc.edu wrote:
>> 
>>> http://sourceware.org/bugzilla/show_bug.cgi?id=13901
>>> 
>>> --- Comment #5 from Jack Howarth <howarth at bromo dot med.uc.edu> 2012-04-02 13:50:37 UTC ---
>>> (In reply to comment #4)
>>>> No, that's a different issue: you haven't configured gdb for x86-64.
>>>> Try with: --enable-64-bit-bfd 
>>>> 
>>>> Tristan.
>>> 
>>> Confirmed that --enable-64-bit-bfd solves the problem debugging x86_64
>>> binaries.
>>> Considering that the pool of EMT64 capable Intel macs greatly outways that of
>>> non-EMT64
>>> units, shouldn't configure default to adding --enable-64-bit-bfd for
>>> i386-apple-darwin?
>> 
>> 
>> No, to be in line with all other platforms: there is a performance impact on
>> bfd side.
> 
> Tristan,
>   How bad is the performance impact?

All address handling in bfd will be 64 bits instead of 32 bits.

> I suspect that fink will want the i386
> fink
> gdb package to support x86_64 binaries as well. Also perhaps the error handling
> for 
> the default build of i386 gdb could be improved. It would be nicer if the
> default
> i386 build of gdb simply refused to load x86_64 binaries and emitted an error
> message
> indicating that the gdb wasn't built with --enable-64-bit-bfd to aid end-users
> with 
> solving the problem.

There is already a generic error message:

warning: A handler for the OS ABI "Darwin" is not built into this configuration
of GDB.  Attempting to continue with the default i386:x86-64 settings.

Not very user friendly, I agree.

IMHO, this is an issue for fink maintainers, most final users don't compiler
gdb themselves.

Might be interesting to understand how ELF handles that.

Tristan.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-04-02 14:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25  1:05 [Bug gdb/13901] New: " howarth at bromo dot med.uc.edu
2012-03-25  1:05 ` [Bug gdb/13901] " howarth at bromo dot med.uc.edu
2012-03-25  1:31 ` howarth at bromo dot med.uc.edu
2012-04-02 11:57 ` cvs-commit at gcc dot gnu.org
2012-04-02 12:00 ` gingold at adacore dot com
2012-04-02 13:14 ` howarth at bromo dot med.uc.edu
2012-04-02 13:20 ` gingold at adacore dot com
2012-04-02 13:51 ` howarth at bromo dot med.uc.edu
2012-04-02 13:58 ` gingold at adacore dot com
2012-04-02 14:35 ` howarth at bromo dot med.uc.edu
2012-04-02 14:41 ` gingold at adacore dot com [this message]
2012-04-11 13:18 ` cvs-commit at gcc dot gnu.org
2012-04-11 13:43 ` cvs-commit at gcc dot gnu.org
2014-02-16 18:28 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org

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=bug-13901-4717-rDyLOvCOQ7@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).