Article View: gnu.gdb.bug
Article #8841gdb 4.6 sloooow
From: Urs Hoelzle
Date: Fri, 16 Oct 1992 17:49
Date: Fri, 16 Oct 1992 17:49
17 lines
1427 bytes
1427 bytes
Has anyone else experienced performance problems with gdb 4.6 when debugging C++ programs (compiled with g++ 2.2.2)? In my (large) program, it often takes several seconds of CPU time (on a Sparc-2) to evalute a simple expression or to display a stack frame. With stack frames, some are fast and some are always very slow (even when displaying them for the second or third time, i.e. it's not a startup problem). I have recompiled gdb twice (with two different compiler and making sure optimization was turned on), with no effect. Also, there's absolutely no problem with paging. -Urs ---------------------------------------------------------------------------- Urs Hoelzle urs@cs.stanford.EDU Computer Systems Laboratory, CIS 57, Stanford University, Stanford, CA 94305
Technical Details
Message-ID:
<hoelzle.719257770@Xenon.Stanford.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!xenon.stanford.edu!hoelzleShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f5053,2a623cbb66b2f756,start X-Google-Attributes: gidf5053,public X-Google-ArrivalTime: 1992-10-16 19:06:30 PST Newsgroups: gnu.gdb.bug Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!xenon.stanford.edu!hoelzle From: hoelzle@xenon.stanford.edu (Urs Hoelzle) Subject: gdb 4.6 sloooow Message-ID: <hoelzle.719257770@Xenon.Stanford.EDU> Sender: gnulists@ai.mit.edu Organization: CS Department, Stanford University, California, USA Distribution: gnu Date: Fri, 16 Oct 1992 17:49:30 GMT Approved: bug-gdb@prep.ai.mit.edu Lines: 19