From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3706 invoked by alias); 27 Nov 2012 02:02:29 -0000 Received: (qmail 3616 invoked by uid 22791); 27 Nov 2012 02:02:26 -0000 X-SWARE-Spam-Status: No, hits=-5.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from ausxipps301.us.dell.com (HELO ausxipps301.us.dell.com) (143.166.148.223) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Nov 2012 02:02:21 +0000 X-Loopcount0: from 10.175.216.250 From: To: CC: Subject: Re: Will therefore GDB utilize C++ or not? Date: Tue, 27 Nov 2012 02:02:00 -0000 Message-ID: References: <20120330161403.GA17891@host2.jankratochvil.net> <87aa2rjkb8.fsf@fleche.redhat.com> <4F832D5B.9030308@redhat.com> <20121122184637.GA29474@host2.jankratochvil.net> <50B41784.2080606@earthlink.net> In-Reply-To: <50B41784.2080606@earthlink.net> Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: 2012-11/txt/msg00073.txt.bz2 On Nov 26, 2012, at 8:29 PM, Stan Shebs wrote: > ... > People that are space-conscious are already using their own stubs or fork= ed versions of gdbserver. I note for instance that we nearly doubled the s= ize of gdbserver's code when we added target-side tracepoint bits a couple = years ago, and I don't recall any grousing about it getting too big then. = In a world where mega-programs like Firefox fit easily onto a cell phone *n= ow*, I'm not just seeing that any future projects are going to be so tightl= y constrained that gdbserver size is noticeable. >=20 > Stan > stan@codesourcery.com I guess I have to keep repeating it: multi-gigabyte cell phones are NOT exa= mples of space constrained embedded systems. I'm working on an embedded sy= stem that's physically much larger but has only 64 MB for the program store= , and only a gigabyte of memory -- of which only 128 MB is available for th= e OS and user mode processes. Yes, the stock gdbserver as delivered with GBD 7 is acceptable. No, doubli= ng it in size is not something you can just casually propose and assume no = one will object. And I know from previous discussions that the system I'm talking about is n= owhere near the most space constrained of embedded systems under active dev= elopment. So can we please stop this silly assumption that everyone has gi= gabytes to spare? Yes of course, if the GDB project starts to operate on the basis that space= is no object, I can and will fork. But isn't the whole point of open sour= ce projects that, while forking is of course allowed, it isn't something to= be pushed as the best way to use the project? If forking was such a wonde= rful thing, we'd still have EGCS. paul