From: Tristan Gingold <gingold@adacore.com>
To: eranon <eric.anon@laposte.net>
Cc: "gdb@sourceware.org Development" <gdb@sourceware.org>
Subject: Re: 'Cannot find bounds of current function' when stepping with GDB 7.6 under OS X 10.6 / LLVM GCC 4.2
Date: Fri, 07 Feb 2014 08:55:00 -0000 [thread overview]
Message-ID: <08E9B682-FE2A-4573-B07C-65DAA46E491A@adacore.com> (raw)
In-Reply-To: <1391709396082-259954.post@n7.nabble.com>
On 06 Feb 2014, at 18:56, eranon <eric.anon@laposte.net> wrote:
> Thanks for this informed info, Tristan. I keep track that it's on your TODO
> list ;)
>
> And I suppose this is not configurable by a switch/flag/option at LLVM GCC
> 4.2 side (to produce a FSF gdb compliant binaries of course) ?
This is a linker issue: try to link with -Wl,-no_compact_unwind (IIRC).
> Also, another question for another approach : Is it possible to go with FSF
> GCC (ie. not the Apple-LLVM one) under OS X ?
Yes, but AFAIK ObjC isn't up to date.
Tristan.
next prev parent reply other threads:[~2014-02-07 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 12:24 eranon
2014-02-06 15:10 ` eranon
2014-02-06 15:31 ` Tristan Gingold
2014-02-06 17:56 ` eranon
2014-02-07 8:55 ` Tristan Gingold [this message]
2014-02-07 20:00 ` eranon
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=08E9B682-FE2A-4573-B07C-65DAA46E491A@adacore.com \
--to=gingold@adacore.com \
--cc=eric.anon@laposte.net \
--cc=gdb@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