From: Simon Marchi <simon.marchi@polymtl.ca>
To: Reinaldo Molina <me@molinamail.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: gdb refuses to connect to localhost
Date: Fri, 25 Dec 2020 19:00:41 -0500 [thread overview]
Message-ID: <9349ff8c-50b3-0a4c-88d4-e295d9b82ba2@polymtl.ca> (raw)
In-Reply-To: <20201225234536.fm6nyuulhw54lhwi@molinamail.com>
On 2020-12-25 6:45 p.m., Reinaldo Molina wrote:
> Thanks for the quick reply.
>
> Trying your suggestion:
>
> Terminal 1:
>
> gdbserver 127.0.01:8889 build/luajit --remote-debug
>
> Terminal 2:
>
> > gdb build/luajit
> GNU gdb (GDB) 10.1
> Copyright (C) 2020 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-pc-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <https://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from build/luajit...
> (gdb) set debug remote 1
> (gdb) target remote localhost:8889
> Remote debugging using localhost:8889
> Sending packet: $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386#6a...Sending packet: $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386#6a...Sending packet: $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386#6a...Sending packet: $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386#6a...Timed out.
> Timed out.
> Timed out.
> Ignoring packet error, continuing...
> Packet qSupported (supported-packets) is supported
> warning: unrecognized item "timeout" in "qSupported" response
> Sending packet: $vMustReplyEmpty#3a...Sending packet: $vMustReplyEmpty#3a...Sending packet: $vMustReplyEmpty#3a...Sending packet: $vMustReplyEmpty#3a...Timed out.
> Timed out.
> Timed out.
> Ignoring packet error, continuing...
> Remote replied unexpectedly to 'vMustReplyEmpty': timeout
> (gdb) target remote 0.0.0.0:8889
> Remote debugging using 0.0.0.0:8889
> Sending packet: $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386#6a...Sending packet: $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386#6a...Sending packet: $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386#6a...Sending packet: $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386#6a...Timed out.
> Timed out.
> Timed out.
> Ignoring packet error, continuing...
> Packet qSupported (supported-packets) is supported
> warning: unrecognized item "timeout" in "qSupported" response
> Sending packet: $vMustReplyEmpty#3a...Sending packet: $vMustReplyEmpty#3a...Sending packet: $vMustReplyEmpty#3a...Sending packet: $vMustReplyEmpty#3a...Timed out.
> Timed out.
> Timed out.
> Ignoring packet error, continuing...
> Remote replied unexpectedly to 'vMustReplyEmpty': timeout
> (gdb) target remote 127.0.0.1:8889
> 127.0.0.1:8889: Connection timed out.
Ok, I don't really know. I'd probably try to strace gdbserver to see
if it at least accepts the incoming connection, and if so what happens
after that.
Simon
next prev parent reply other threads:[~2020-12-26 0:00 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 [this message]
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
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=9349ff8c-50b3-0a4c-88d4-e295d9b82ba2@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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).