Dan

So, I take it the log outputs you're showing are from the 14.1-1 and 13.2-3 packages? The fact that the log believes it's CLI instead of MI2 indicates one of...

I'm scraping the bottom of the barrel here, unfortunately. I get the following when I run `gdb -i mi2` with gdb-13.1 on Linux, where this is known to work: ```...

@Nemoumbra Yes, it is similar, which is why we're trying to get at the first line. @tehomen I'm glad to see the first line is the event. Still, we're seeing...

I've got a little extra time today. I may obtain a copy of gdb-14.1 and see if I can reproduce this. I'm surprised to see the same problem via SSH....

Here's what I've tried so far: I've built and install gdb-14.1 on Linux, then using our development branch of Ghidra, I connected to it in a variety of ways: With...

Okay, It Works on My Machine (TM) for gdb-14.1 in Windows as well. I'll do my best to capture everything I did in case you want to try repeating it...

GDB via SSH to Linux should work with or without that workaround. Not sure why Ghidra is having trouble running GDB on its own (i.e., without new-ui) on your setup....

Wow. Thank you for the thorough write up! So, the bit that catches my eye (finally), is the log line for ghidraDebug.bat: > ``` > DEBUG STDOUT,null reader exiting because...

I already think my guess is off. The private commands have a question mark in them, and I already have code that's supposed to handle that. So, either the exception...

Well. Okay then! I guess I'll merge the change. I'm still a bit mystified as to why, but I guess unless I can get a hold of the same build...