Hello
1. When using SES with GDB server for debugging, SES would send packages like '$vCont;s:0#22' '$vCont;c:0#12'. It uses thread id 0 here which means 'an arbitrary thread' according to GDB protocol.
Some GDB server does not accept such an ambiguous identity, could SES team change the id from 0 to 1 which means the first thread or change to -1 to represent all threads?
2. SES does not support GDB RLE, which uses * to represent a bunch of repetive data. Could SES team add support for it?
1. When using SES with GDB server for debugging, SES would send packages like '$vCont;s:0#22' '$vCont;c:0#12'. It uses thread id 0 here which means 'an arbitrary thread' according to GDB protocol.
Some GDB server does not accept such an ambiguous identity, could SES team change the id from 0 to 1 which means the first thread or change to -1 to represent all threads?
2. SES does not support GDB RLE, which uses * to represent a bunch of repetive data. Could SES team add support for it?