From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9692 invoked by alias); 17 Nov 2003 15:18:44 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9684 invoked from network); 17 Nov 2003 15:18:43 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 17 Nov 2003 15:18:43 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id KAA04733 for ; Mon, 17 Nov 2003 10:33:02 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id KAA05342 for ; Mon, 17 Nov 2003 10:18:40 -0500 Message-ID: <03e601c3ad1e$3b2f0ff0$0202040a@catdog> From: "Kris Warkentin" To: "Gdb@Sources.Redhat.Com" Subject: [RFC] upload/download command Date: Mon, 17 Nov 2003 15:18:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-11/txt/msg00122.txt.bz2 Our QNX pdebug protocol supports an upload/download command. This is handy for putting binaries onto target system and getting back things like corefiles. Andrew had wanted me to start a discussion on the subject. I would like to keep these things in our protocol but it might be useful to generalize the interface out to core gdb. What I'm thinking is that I create a general upload/download command that uses a hook into the target's code for any special functionality. We could have a general one for native targets which would basically be 'copy' (probably not all that useful but there for completeness) and just print 'not implemented' for targets which don't define the hooks. Any ideas, comments, suggestions, etc.? cheers, Kris