Re: gdb refuses to connect to localhost
Simon Marchi via Gdb <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <[email protected]> |
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