From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6433 invoked by alias); 9 Oct 2006 19:00:44 -0000 Received: (qmail 6424 invoked by uid 22791); 9 Oct 2006 19:00:43 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Mon, 09 Oct 2006 19:00:39 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GX0Mf-0005uS-85 for gdb@sourceware.org; Mon, 09 Oct 2006 15:00:37 -0400 Date: Mon, 09 Oct 2006 19:00:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Is GDB support for IPv6 useful? Message-ID: <20061009190037.GA22579@nevyn.them.org> Mail-Followup-To: gdb@sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00044.txt.bz2 Jan Kratochvil posted patches on the gdb-patches mailing list which add support for both "target remote" connecting to IPv6 targets, and gdbserver listening on IPv6 targets. You can already simulate this behavior for GDB, by using "target remote |" in combination with a helper like socat. If support were added to gdbserver for using arbitrary file descriptors - not hard, as you can see from Jan's latest patch - it could do the same. But what I'm really interested in is whether native IPv6 support would be useful for GDB. If it is, we should go ahead and merge it. If no one or almost no one is ever going to want it, then we shouldn't, and I can write up some text for the manual about how to use an external program to implement it. I have never used IPv6, for debugging or anything else, so I don't feel able to make a useful decision about this. I'd like to hear from some people who do use it. -- Daniel Jacobowitz CodeSourcery