Hello again! I captured with wireshark the communication. They do seem to communicate is just it seems gdbserver is sending this weird stuff that I don't know. I guess you guys neither if it does not look familiar: > > 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. I have attached the raw wireshark capture of the communication. I am not too versed in networking so I don't see anything out of line other than gdbserver sending the above weird stuff. I have tried multiple things. Just debugging a simple hello world, I checked pacman to see if any of the default installed files have been altered and they have not, I removed `.gdbinit`. The `gdb` installation is the default one from `pacman`: https://archlinux.org/packages/extra/x86_64/gdb/ Just really strange behavior. I have a desktop and a laptop and I can reproduce the same behavior in both. They are both very similar in linux setup, packages, etc. Just really scratching my head here. Thanks, Reinaldo Molina On 12-25-20 19:00:41, Simon Marchi wrote: > > > 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 > > 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: > > . > > Find the GDB manual and other documentation resources online at: > > . > > > > 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