From: Keith Seitz <keiths@redhat.com>
To: Hugh Sparks <hugh@csparks.com>
Cc: insight@sourceware.org
Subject: Re: Steps to build Insight for Windows
Date: Thu, 10 Jan 2013 22:47:00 -0000 [thread overview]
Message-ID: <50EF450A.9050708@redhat.com> (raw)
In-Reply-To: <50EF2892.5040800@csparks.com>
On 01/10/2013 12:46 PM, Hugh Sparks wrote:
> The CVS browser does work and I could see an expat directory. Evidently
> the archives I tried are too old? Is there somewhere I can download the
> appropriate sources? Any insight into why source code doesn't
> appear in the debugger would be appreciated.
Yes, the tarballs you downloaded are quite old, indeed. I keep meaning
to make an official release, but life has really gotten in the way. My bad.
The easiest thing to do is checkout the latest sources from CVS HEAD. If
you can't do that, let me know, and I'll tar up a copy and either send
it to you or put it somewhere you can get at it.
As for the source files not being found, I would first try opening a
console window and typing "list" or "list <SOMEF UNCTION>". If that
doesn't get you source, either, then you will need to modify the source
search path using gdb's "dir" command (type "help dir" into the console
for help on that).
The other thing to check is that you really do have debug info. For a
function defined in the source file you cannot list, type "info func
<FUNCNAME>". Gdb will tell you whether it has any debuginfo for that
function. If it only gives "Non-debugging symbols", then your CU was not
actually built with debuginfo (or it was stripped, damaged, etc).
Keith
next prev parent reply other threads:[~2013-01-10 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1357848662.20894.ezmlm@sourceware.org>
2013-01-10 20:46 ` Hugh Sparks
2013-01-10 22:47 ` Keith Seitz [this message]
2012-11-02 10:06 Roland Schwingel
-- strict thread matches above, loose matches on Subject: below --
2012-11-01 6:29 Kobus Engelbrecht
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=50EF450A.9050708@redhat.com \
--to=keiths@redhat.com \
--cc=hugh@csparks.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).