Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Thu, 06 Feb 2014 15:31:00 -0000	[thread overview]
Message-ID: <71D481D3-CF88-453D-9BB5-561D6AEFE8A9@adacore.com> (raw)
In-Reply-To: <1391699417056-259908.post@n7.nabble.com>


On 06 Feb 2014, at 16:10, eranon <eric.anon@laposte.net> wrote:

> What I get could look like what expressed in this thread : 
> http://sourceware-org.1504.n7.nabble.com/gdb-can-not-debug-hello-world-in-mac-os-x-td107600.html
> 
> In addition to the error I told about, at the same time, hitting the "n"
> command, I get something like this too :
> 
> (gdb) n 
> 0x00003045 in ?? ()
> 
> So, the question is maybe : What FSF gdb version should I use to debug a
> i386 DEBUG build coming from the LLVM GCC 4.2 shipped with Xcode 4.2 under
> OS X 10.6 (and I have OS X 10.8 with Xcode 4.6 too, but didn't installed my
> dev environment in full under this station yet) ?

I am almost sure that FSF gdb doesn't support binaries produced by recent version of
LLVM shipped by xcode.  They use compact unwinding, which isn't handled by gdb.
This is on my todo list, but not that urgent because FSF gcc doesn't emit them (it
passes -no_compact_unwind to ld).


  reply	other threads:[~2014-02-06 15:31 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 [this message]
2014-02-06 17:56     ` eranon
2014-02-07  8:55       ` Tristan Gingold
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=71D481D3-CF88-453D-9BB5-561D6AEFE8A9@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