From: Andrea Crotti <andrea.crotti.0@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: finally getting gdb to work?
Date: Thu, 22 Jul 2010 10:04:54 +0200 [thread overview]
Message-ID: <m1r5iw3psp.fsf@gmail.com> (raw)
I don't understand what happens here, yesterday for the first time I saw
how I should be supposed to debug in emacs (with gdb).
It was great, jumping, easily set breakpoints and so on.
By default this "gdb-many-windows" is nil and until I didn't set it to
"t" I thought that text-mode stuff was all I was getting.
After some other time and trying also out pdb then nothing works
anymore!
When I run
M-x gdb test
I don't anymore the windows set, and if I call gdb-restore-windows I
don't get a working debug environment anyway (only the windows set).
Here is my very simple conf
--8<---------------cut here---------------start------------->8---
#+begin_src emacs-lisp :tangle yes
(setq gdb-show-main nil)
(setq gdb-many-windows t)
#+end_src
*** Some advices for pdb
#+begin_src emacs-lisp :tangle yes
(defadvice pdb (before gud-query-cmdline activate)
"Provide a better default command line when called interactively."
(interactive
(list (gud-query-cmdline 'pdb.py
(file-name-nondirectory buffer-file-name)))))
#+end_src
--8<---------------cut here---------------end--------------->8---
Anyone has an idea?
Ah another thing, I also have to debug some code which compiles only on
a virtual machine, which I can access via ssh.
Now I work on it via sshfs, but I would like to debug it directly.
Is there some way to automate the debugging process from another
machine (with gdbserver or tramp maybe?)?
Thanks a lot
next reply other threads:[~2010-07-22 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 8:04 Andrea Crotti [this message]
2010-07-22 10:41 ` finally getting gdb to work? Michael Albinus
2010-07-22 11:12 ` Andrea Crotti
2010-07-22 11:20 ` Andrea Crotti
2010-07-22 12:01 ` Bastian Beischer
2010-07-22 11:49 ` Michael Albinus
2010-07-22 11:58 ` Andrea Crotti
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=m1r5iw3psp.fsf@gmail.com \
--to=andrea.crotti.0@gmail.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).