On Feb 9, 2008 7:25 PM, Philippe Waroquiers <[EMAIL PROTECTED]> wrote: > The gdb documentation looks reasonably clear at first sight, but of course > it does not mean that it is correct and/or that the implementation of the > protocol > is correct. At what time did you work with this remote protocol ?
It was about two years ago that I last reported a bug that was related to the gdb - gdbserver communication protocol. A quick look in the gdb bugzilla shows that there still may be issues with the remote debugging protocol implementation: http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=2301&return_url=http%3A%2F%2Fsourceware.org%2Fcgi-bin%2Fgnatsweb.pl%3Fdatabase%3Dgdb%26category%3Dall%26severity%3Dall%26priority%3Dall%26responsible%3Dall%26submitter_id%3Dall%26state%3Dall%26ignoreclosed%3DIgnore%2520Closed%26class%3Dall%26synopsis%3D%26multitext%3Dgdbserver%26columns%3Dcategory%26columns%3Dstate%26columns%3Dclass%26columns%3Dresponsible%26columns%3Dsynopsis%26displaydate%3DDisplay%2520Current%2520Date%26cmd%3Dsubmit%2520query%26sortby%3DResponsible%26.cgifields%3Ddisplaydate%26.cgifields%3Dignoreclosed%26.cgifields%3Doriginatedbyme%26.cgifields%3Dcolumns There also exists an enhanced version of gdbserver, called rproxy. Unfortunately the homepage of this project is no longer accessible (http://world.std.com/~qqi/labslave/rproxy.html). Bart Van Assche. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers