Re: fix remote serial read

["Сергей Чернов" <klen_s@mail.ru>]

[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]


Hello Tom!
 
my git client did not allow me to make a email-like patch automatically (for some reason it works with an error) and I, knowing the format, wrote it by hand... apparently I work no better than him :)
Thank you for making the correction to trunk gdb sources, I will be pleased if my name is mentioned :)
Every day I develop tools for developing and debugging embedded devices based on cortex-m and little riscv - so I detect errors with GCC and GDB local and remote hardware debugging immediately. At the same time, I have accumulated patches that could be offered to the public. Perhaps it would be nice if we collaborated for the common good.
There are ideas on how to improve riscv debugging in the direction of indicating only the actually implemented special registers (SCR) of the processor. I plan to try this and will share the result for discussion. I'm involved in improving the GCC target-port ror RISCV and apparently this could be matched by an improvement in bu/gdb.
 
Best regards
Chernov Sergey aka Klen Santakheza
>Пятница, 19 января 2024, 21:02 +03:00 от Tom Tromey <tom@tromey.com>:
> 
>>>>>> Сергей Чернов < klen_s@mail.ru > writes:
> 
>> After closing "Bug 30770 - serial.c does not preserve errno correctly"
>>  https://sourceware.org/bugzilla/show_bug.cgi?id=30770
>> remote debugging became impossible due to an attempt to recv() by a call intended for the socket, and not for the character device file. The
>> documentation implicitly states that it is possible to use the read() call to work with a socket. But this does not mean in the general case that it is
>> permissible to use recv in the case of a non-socket.  
>This patch wasn't sent in a way that was easy to apply, but I've gone
>ahead and done it manually. I'm going to push it shortly.
>
>Tom