From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30314 invoked by alias); 26 Oct 2006 07:11:47 -0000 Received: (qmail 30303 invoked by uid 22791); 26 Oct 2006 07:11:45 -0000 X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (199.232.76.164) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 26 Oct 2006 07:11:42 +0000 Received: from eliz by fencepost.gnu.org with local (Exim 4.34) id 1GczOt-0007eK-Nq; Thu, 26 Oct 2006 03:11:39 -0400 From: Eli Zaretskii To: Russell Shaw CC: gdb@sourceware.org In-reply-to: <45401D58.4010109@netspace.net.au> (message from Russell Shaw on Thu, 26 Oct 2006 12:28:40 +1000) Subject: Re: Gdb Reply-to: Eli Zaretskii References: <453F0CA7.7070309@netspace.net.au> <20061025124921.GA15974@nevyn.them.org> <453F68E9.9050800@netspace.net.au> <45401D58.4010109@netspace.net.au> Message-Id: Date: Thu, 26 Oct 2006 07:11:00 -0000 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/msg00254.txt.bz2 > Date: Thu, 26 Oct 2006 12:28:40 +1000 > From: Russell Shaw > CC: gdb@sourceware.org > > > That is not necessarily a sign of bad design. For example, when Emacs > > does garbage collection, the stack depth sometimes exceeds 10,000 > > levels when recursive data structures are marked. That is normal and > > by design. > > The slowness and size of emacs put me off it. I use (g)vim because > editing using ex regex commands is a more direct way at doing things imho. What does this have to do with the issue at hand? I used Emacs as an example of a very deep stack being a normal situation in a working program whose design is generally considered well-thought. > > Perhaps you lack good tools for learning programs, or don't use them > > to their full power. > > I just use ctags to navigate in gvim. I recommend to add at least ID-Utils to your toolchest. I don't know if someone wrote a gvim plug-in for it (the Emacs interface is included in the package), but even if you invoke it from the shell, it's an invaluable tool for finding your way around an unfamiliar program. Also, some parts of GDB internals are documented in gdbint.texinfo. Sadly, many important aspects are not covered at all there, but if you are lucky to be working on something that is described, reading that manual can help.