From: tom fogal <tfogal@apollo.sr.unh.edu>
To: gdb@sources.redhat.com
Subject: force scanning of includes?
Date: Mon, 08 Aug 2005 17:12:00 -0000 [thread overview]
Message-ID: <200508081712.j78HCUYa032711@apollo.sr.unh.edu> (raw)
This is probably in the docs somewhere, but my greps are coming up
empty. sorry.
I'm trying to debug a C++ program, and gdb doesn't seem to know about
objects defined in a library. The library is built with -g and
installed in /usr/local/lib/vtk, which is listed in /etc/ld.so.conf.
The headers are in /usr/local/include/vtk.
When I try to print an instance of an object from the library, gdb
thinks it is a struct:
#10 0x000000000040825c in main (argc=1, argv=0x7fffffffe748) at test.cxx:60
60 Renderer->Delete();
(gdb) print Renderer
$1 = (struct vtkRenderer *) 0x52d5b0
(gdb) print *Renderer
$2 = <incomplete type>
How can I tell gdb to scan /usr/local/include/vtk/vtkRenderer.h, so it
will know what a vtkRenderer is? The 'directories' command doesn't seem
to be much use here.
I've tried compiling my test.cxx program with '-g' and later '-gdwarf-2
-g3' after reading through some archives.
Thanks,
-tom
next reply other threads:[~2005-08-08 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 17:12 tom fogal [this message]
2005-08-08 20:57 ` Jason Molenda
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=200508081712.j78HCUYa032711@apollo.sr.unh.edu \
--to=tfogal@apollo.sr.unh.edu \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).