From: Geert Vancompernolle <gvcompernolle@scarlet.be>
To: Keith Seitz <keiths@redhat.com>
Cc: Insight Foum <insight@sourceware.org>
Subject: Re: Problems with function pointers in C++
Date: Thu, 21 Feb 2008 18:58:00 -0000 [thread overview]
Message-ID: <47BDC98A.4000104@scarlet.be> (raw)
In-Reply-To: <47BC84C5.5090006@redhat.com>
Keith Seitz wrote:
>
>
> But perhaps I am mistaken about this being the problem...
>
Well, I just recompiled that code for the PC, not for my embedded Linux
system. But when I try to load the source into Insight, I still get
only assembly code, I don't see the HLL code...
Don't know why... When using Insight in combination with my external
embedded Linux board, it's working like a breeze (apart from the C++
pointer problems), when using Insight to debug a PC application, it's
not working. Never did debug a PC program before on Linux, though...
So, how can I get out of this...
--
*Best rgds,
--Geert
*
next prev parent reply other threads:[~2008-02-21 18:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 14:40 Geert Vancompernolle
2008-02-17 19:38 ` Keith Seitz
2008-02-18 4:03 ` Geert Vancompernolle
2008-02-18 4:07 ` Geert Vancompernolle
2008-02-18 7:09 ` Keith Seitz
2008-02-19 18:51 ` Geert Vancompernolle
2008-02-19 19:00 ` Geert Vancompernolle
2008-02-19 19:20 ` Geert Vancompernolle
2008-02-19 19:59 ` Keith Seitz
2008-02-20 18:24 ` Geert Vancompernolle
2008-02-20 19:03 ` Keith Seitz
2008-02-20 19:30 ` Geert Vancompernolle
2008-02-20 19:35 ` Keith Seitz
2008-02-20 19:48 ` Geert Vancompernolle
2008-02-20 19:53 ` Keith Seitz
2008-02-21 18:58 ` Geert Vancompernolle [this message]
2008-02-21 19:04 ` Keith Seitz
2008-02-21 19:33 ` Geert Vancompernolle
2008-02-21 19:49 ` Keith Seitz
2008-02-22 18:09 ` Geert Vancompernolle
2008-02-22 19:53 ` Keith Seitz
2008-02-24 10:03 ` Geert Vancompernolle
2008-02-24 18:34 ` Keith Seitz
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=47BDC98A.4000104@scarlet.be \
--to=gvcompernolle@scarlet.be \
--cc=insight@sourceware.org \
--cc=keiths@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).