From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: vijay nag <vijunag@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: cannot find bounds of function error
Date: Wed, 24 Jul 2013 12:39:00 -0000 [thread overview]
Message-ID: <20130724123924.GB4376@host2.jankratochvil.net> (raw)
In-Reply-To: <CAKhyrx8aDzz78UgWjUN78q7pWZ0=-Y3KH8oOkFb3P2RCK+F52Q@mail.gmail.com>
On Wed, 24 Jul 2013 11:44:15 +0200, vijay nag wrote:
> My latest gdb-7.5 barfs out "cannot find bounds of current function"
> error when it encounters GNU_IFUNC while executing one line of code at
> a time using "next" command
Sorry I did not analyze exactly your case but ensure your glibc contains this
patch fixing how GDB deals with gnu-ifuncs:
commit f85fa27058eb7d4b56b8deaf885064cf8d730f68
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Thu Aug 9 16:04:37 2012 -0700
Avoid DWARF definition DIE on ifunc symbols
Besides that there is already stable gdb-7.6 but I do not know about any
specific change there for gnu-ifunc.
Jan
next prev parent reply other threads:[~2013-07-24 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 9:44 vijay nag
2013-07-24 12:39 ` Jan Kratochvil [this message]
[not found] ` <CAKhyrx_LP-rqJMN_CoJ_Hy9X8+1or9CTQab=ioHBfnFBVjQ-nQ@mail.gmail.com>
2013-07-24 13:28 ` vijay nag
2013-08-13 8:59 ` vijay nag
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=20130724123924.GB4376@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=vijunag@gmail.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