From: karsten.ahnert@googlemail.com
To: gnu.emacs.help@googlegroups.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: gud and shared objects
Date: Thu, 27 Dec 2012 11:53:59 -0800 (PST) [thread overview]
Message-ID: <64ad331f-a820-4a76-a0f3-586c50c5e46a@googlegroups.com> (raw)
In-Reply-To: <mailman.16153.1356580485.855.help-gnu-emacs@gnu.org>
Am Donnerstag, 27. Dezember 2012 04:54:17 UTC+1 schrieb Eli Zaretskii:
> > Date: Wed, 26 Dec 2012 21:53:01 +0100
>
> > From: Karsten Ahnert <karsten.ahnert@googlemail.com>
>
> >
>
> > I have a problem with debugging C++ with emacs and gdb. I can set
>
> > breakpoints in functions defined in shared objects by simply adding them
>
> > manually via
>
> >
>
> > b file_in_so.cpp:23
>
> >
>
> > But if I open file_in_so.cpp in an emacs window I can not use the
>
> > graphical debugging facilities. I guess, that emacs does not yet know
>
> > that this file belongs to the sources of the executable. Files belonging
>
> > not to the shared object are already usable for graphical debugging.
>
> > Files from the shared object are also usable if a manual breakpoint or
>
> > an uncaught exception are hit within the shared object.
>
> >
>
> > Is there a command telling emacs to reload the current list of all
>
> > sources, even the ones defined in shared objects?
>
>
>
> This is a GDB issue, not an Emacs issue. Try using the GDB command
>
> "set auto-solib add on".
That does also not work. I can see that the shared object has already been loaded by gdb but the source files are not correctly shown in emacs. Maybe this is a path issue?
prev parent reply other threads:[~2012-12-27 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 20:53 gud and shared objects Karsten Ahnert
2012-12-27 3:54 ` Eli Zaretskii
[not found] ` <mailman.16153.1356580485.855.help-gnu-emacs@gnu.org>
2012-12-27 19:53 ` karsten.ahnert [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=64ad331f-a820-4a76-a0f3-586c50c5e46a@googlegroups.com \
--to=karsten.ahnert@googlemail.com \
--cc=gnu.emacs.help@googlegroups.com \
--cc=help-gnu-emacs@gnu.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).