From: Zhongwei Yao <ashi08104@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: How to make gdb debug mode work with tramp?
Date: Sun, 3 Sep 2017 22:10:45 +0800 [thread overview]
Message-ID: <CAJnfWeHGyQ6TbU71SFDK=uMBVM5t=Z2AHabGHCw3aynb_4-0xA@mail.gmail.com> (raw)
Hi, all,
I try to use 'M-x gdb' on Mac with tramp. But it runs into varies errors.
Here are some details:
Environment:
emacs 25.1.1 runs on Mac with tramp 2.2.13.25.1. And I have a test project
on a raspberry pi directory: /home/xxx/project/test_gdb/. It has a simple
file: test.c. test.c is compiled by gcc with -O0 -g to test_bin.
test.c:
1 int foo(int a, int b) {
2 int c = a + b;
3 return c;
4 }
5
6 int main(void) {
7 return foo(3, 4);
8 }
Steps:
1. Open test.c on raspberry pi in emacs
2. run 'M-x gdb' gdb -i=mi test_bin and open gdb-many-window mode.
3. In *gud-test* buffer, run: break 7
Then I get an error in emacs Message:
File /scp:xxx@my-rasp-pi:/home/xxx/project/test_gdb/"/home/xxx/project/test_gdb/test.c"
no longer exists!
And in *gud-test* buffer, it prints following:
=== gud-test content start ===
96 Breakpoint 1 at 0x103c4: file test.c, line 7.
97 (gdb) list test.c:1
98 1 int foo(int a, int b) {
99 2 int c = a + b;
100 3 return c;
101 4 }
102 5
103 6 int main(void) {
104 7 return foo(3, 4);
105 8 }
=== gud-test content end ===
line 96 is OK, but I don't know why it prints line 97 to 105. I have not
typed any 'list' command. And it has set a break point on line 7.
4. I continue to run some debug command like: continue, but *gud-test*
buffer stucks until I type "Ctrl+g".
I don't know which part causes such error, gud-mode, tramp-mode or
something else and how to fix it.
Thanks for any suggestion!
--
Regards,
Zhongwei
next reply other threads:[~2017-09-03 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 14:10 Zhongwei Yao [this message]
2017-09-05 6:39 ` How to make gdb debug mode work with tramp? Zhongwei Yao
2017-09-05 14:36 ` Michael Albinus
2017-09-05 15:43 ` Glenn Morris
2017-09-05 19:31 ` Mario Castelán Castro
2017-09-05 22:13 ` Glenn Morris
2017-09-06 7:50 ` Michael Albinus
2017-09-06 15:13 ` Zhongwei Yao
2017-09-07 10:23 ` Michael Albinus
2017-09-07 12:30 ` Zhongwei Yao
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='CAJnfWeHGyQ6TbU71SFDK=uMBVM5t=Z2AHabGHCw3aynb_4-0xA@mail.gmail.com' \
--to=ashi08104@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).