From: Martin Simmons <qqxnjvamvxwx@dyxyl.com>
To: Reinaldo Molina <me@molinamail.com>
Cc: gdb@sourceware.org
Subject: Re: gdb refuses to connect to localhost
Date: Tue, 29 Dec 2020 15:48:39 +0000 [thread overview]
Message-ID: <jeeej84nqg.fsf@dyxyl.com> (raw)
In-Reply-To: <20201225223622.a7xovhjzndth5a2x@molinamail.com> (message from Reinaldo Molina via Gdb on Fri, 25 Dec 2020 17:36:22 -0500)
>>>>> On Fri, 25 Dec 2020 17:36:22 -0500, Reinaldo Molina via Gdb said:
>
> Hey guys!
>
> Looking for some assistants here. I am trying to debug an application using `gdbserver`, but it seems my `lo` network device is messed up. `gdb` refuses to connect to `localhost` every time. Here is my flow:
>
> Terminal 1: `gdbserver localhost:8888 build/luajit`
> - Variants I've tried: `127.0.0.1:8888`
>
> Terminal 2: `gdb build/luajit -ex 'target remote localhost:8888'`
>
> Output from `gdb` on Terminal 2:
>
> (gdb) target remote :8888
> Remote debugging using :8888
> Ignoring packet error, continuing...
> warning: unrecognized item "timeout" in "qSupported" response
> Ignoring packet error, continuing...
> Remote replied unexpectedly to 'vMustReplyEmpty': timeout
Try running gdbserver with the --no-startup-with-shell argument:
gdbserver --no-startup-with-shell localhost:8888 build/luajit
That seems to be necessary if your shell is tcsh.
__Martin
next prev parent reply other threads:[~2020-12-29 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 22:36 Reinaldo Molina
2020-12-25 22:55 ` Simon Marchi
2020-12-25 23:45 ` Reinaldo Molina
2020-12-26 0:00 ` Simon Marchi
2020-12-28 15:56 ` Reinaldo Molina
2020-12-28 22:29 ` Simon Marchi
2020-12-25 23:04 ` Andreas Schwab
2020-12-26 0:00 ` Reinaldo Molina
2020-12-29 15:48 ` Martin Simmons [this message]
2020-12-29 15:58 ` Reinaldo Molina
2020-12-29 21:18 ` Simon Marchi
2020-12-30 1:20 ` Reinaldo Molina
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=jeeej84nqg.fsf@dyxyl.com \
--to=qqxnjvamvxwx@dyxyl.com \
--cc=gdb@sourceware.org \
--cc=me@molinamail.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).