Potential SIS or RTEMS/libbsd problem
Chris Johns
chrisj at rtems.org
Mon Jun 3 21:45:18 UTC 2019
On 3/6/19 5:51 pm, Jiri Gaisler wrote:
>
> On 6/3/19 4:14 AM, Chris Johns wrote:
>> On 1/6/19 6:58 am, Jiri Gaisler wrote:
>>> I have pushed a small patch to fix some build problems on Cygwin and FreeBSD. I don't know how fast we want to progress, but I could prepare a patch for RSB to use the new sis repository and skip the sis patches for gdb. I guess this would also have include updating any documentation that refers to the old sis ...
>> I am happy to move to using a separate sis executable built by the RSB and for
>> the gdb versions and patches to stop being maintained.
> OK, I will look at this on some rainy day ...
>>
>> By the way have you looked at the GDB pipe interface to the a remote executable?
>> It would be interesting to know how using that transport effects the ^C issue on
>> Windows.
>
> I will check this. However, I thought pipes were unidirectional on linux...?
>
It uses the stdin and stdout of the child process for the remote protocol. It
means you need to send console output over the remote protocol which could be
considered a feature :)
See ...
https://github.com/RTEMS/sourceware-mirror-binutils-gdb/blob/master/gdb/gdbserver/remote-utils.c#L337
The nice thing about using a pipe is gdb handles the external simulator so you
do not need to coordinate two processes. This makes scripting tools like
rtems-test simpler.
Chris
More information about the devel
mailing list