public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kfir Lavi <lavi.kfir@gmail.com>
To: gentoo-user@lists.gentoo.org, gentoo-embedded@gentoo.org
Subject: [gentoo-user] gdb debugging of small system built with catalyst
Date: Sun, 25 Dec 2011 11:20:27 +0200	[thread overview]
Message-ID: <CAHNvW1JOtq1JkVFZs-zH7G1Qj+7EAouwdWNdSk3bKtC8-kScpA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

Hi,
I have few directories each contains C++ code, and is mapped to a local
private ebuild.
So I need to install few projects that depend on each other.
On the target machine I have gdbserver running.
When connecting to gdbserver, the links to the sources is
/var/tmp/.../../file.cpp.
My problem is that I need to debug all programs together, and the sources
are in catalyst's tmp working directory.
I can use 'directory' command in gdb to change the search path of the
source files, but doing it to few projects is cumbersome.
I can compile the source with -g3 and embed the sources there, but didn't
try that as I heard it is unstable.
At the end I need to provide a way to allow programmers to use Eclipse with
all the directories sources to debug all projects at once.
Is there other method to do this and integrate it to Eclipse?
For start no need for eclipse, I need to debug from the command line or vim.
Regards,
Kfir

[-- Attachment #2: Type: text/html, Size: 1028 bytes --]

             reply	other threads:[~2011-12-25  9:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-25  9:20 Kfir Lavi [this message]
2011-12-31 21:20 ` [gentoo-user] Re: [gentoo-embedded] gdb debugging of small system built with catalyst Mike Frysinger
2012-01-02  9:09   ` Kfir Lavi
2012-01-02 19:31     ` [gentoo-user] " Mike Frysinger

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=CAHNvW1JOtq1JkVFZs-zH7G1Qj+7EAouwdWNdSk3bKtC8-kScpA@mail.gmail.com \
    --to=lavi.kfir@gmail.com \
    --cc=gentoo-embedded@gentoo.org \
    --cc=gentoo-user@lists.gentoo.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