From: Lisa McIlrath <lmcilrath@r3logic.com>
To: insight@sourceware.org
Subject: updated gdb source
Date: Wed, 21 Aug 2013 04:01:00 -0000 [thread overview]
Message-ID: <52143BAB.9060401@r3logic.com> (raw)
Hi,
I've been using insight for a number of years and it's great. Thank you!
I recently installed Centos 6 on a development machine and, although
insight will build, it will no longer run properly. After some
investigation I discovered that some patches had been made to the
dwarf2read.c and related sources in the gdb distribution due to the fact
that the int/uint definitions had changed with new versions of gcc. I
applied one patch and got insight to run, or at least not seg fault on
loading a program, only to get an error message down the road about an
'unhandled dwarf expression opcode' when I tried to open the watch window.
So the problem seems to be that the gdb version distributed with the
source is too old. Brilliantly, I thought of replacing it with a newer
gdb source distribution. Unfortunately, that broke the build, and I have
thrown in the towel.
Is there any way to get an updated source version with fresh gdb code
that will build?
I would be eternally grateful if so.
Thanks,
Lisa McIlrath
next reply other threads:[~2013-08-21 4:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 4:01 Lisa McIlrath [this message]
2013-08-21 4:14 ` Keith Seitz
2013-08-21 14:07 ` Lisa McIlrath
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=52143BAB.9060401@r3logic.com \
--to=lmcilrath@r3logic.com \
--cc=insight@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).