From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14606 invoked by alias); 29 Jan 2008 13:58:55 -0000 Received: (qmail 14598 invoked by uid 22791); 29 Jan 2008 13:58:55 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 29 Jan 2008 13:58:35 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 1139E983A6; Tue, 29 Jan 2008 13:58:34 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 9B81898383; Tue, 29 Jan 2008 13:58:33 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1JJqyu-00068M-HG; Tue, 29 Jan 2008 08:58:32 -0500 Date: Tue, 29 Jan 2008 13:58:00 -0000 From: Daniel Jacobowitz To: Pedro Alves Cc: gdb@sourceware.org Subject: Re: Small remote file transfer protocol adition Message-ID: <20080129135832.GB22880@caradoc.them.org> Mail-Followup-To: Pedro Alves , gdb@sourceware.org References: <479EAB6F.8040505@portugalmail.pt> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <479EAB6F.8040505@portugalmail.pt> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00309.txt.bz2 On Tue, Jan 29, 2008 at 04:28:31AM +0000, Pedro Alves wrote: > To be able support this, this proposal adds an optional field > to the reply packet: > > F$(retcode),$(remote_error),$(native_error); I don't like designing an interface that is going to have to show hex numbers to the user. They'd have to figure out that it was a target error number and look it up themselves. Despite the localization issues involved, do you think it might be better to add an error string if you need the extra detail? We could put it in the attachment field. Could you give me an example of a useful error code which does not map to one of the POSIX errors? -- Daniel Jacobowitz CodeSourcery