From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16061 invoked by alias); 2 Jan 2007 15:24:01 -0000 Received: (qmail 16052 invoked by uid 22791); 2 Jan 2007 15:24:00 -0000 X-Spam-Check-By: sourceware.org Received: from wr-out-0506.google.com (HELO wr-out-0506.google.com) (64.233.184.225) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 02 Jan 2007 15:23:54 +0000 Received: by wr-out-0506.google.com with SMTP id i23so1907041wra for ; Tue, 02 Jan 2007 07:23:53 -0800 (PST) Received: by 10.78.149.15 with SMTP id w15mr1931936hud.1167751432443; Tue, 02 Jan 2007 07:23:52 -0800 (PST) Received: by 10.78.136.20 with HTTP; Tue, 2 Jan 2007 07:23:52 -0800 (PST) Message-ID: Date: Tue, 02 Jan 2007 15:24:00 -0000 From: "dodji Seketeli" To: gdb@sourceware.org Subject: gdb very slow during 'step into' MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: f4da906d23d89393 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: 2007-01/txt/msg00012.txt.bz2 Hello gdb hackers and users, First of all, I would like to wish a happy new year to you and your families. I hope this year will be full of achievements (again) for gdb people. Now the real meat of my post :-) I have noticed that gdb was very slow (taking 100% of CPU during several tens of seconds) when I step into some functions (with the step command, on the cli interface). I am not sure, but I think it happens when I step into functions that are defined in certain shared libraries. Once in the function, subsequent steping into functions of the same library are okay. Once out of the library, stepping into a function of that library can be slow again. The problem is that I cannot reproduce this problem all the time. I have straced gdb during one of this slow stepping. You can find the log at http://dodji.seketeli.free.fr/gdb/slow-step-into-trace.txt. The debugged language is C++. I have noticed the problem with gdb 6.4.90, 6.5 and 6.6. My system is debian testing. Are these information valuable to investigate the problem ? If yes, I can file a bug in the gnatsweb application if you wish. If not, please tell me what information I can add to make provide you guys with valuable information. Cheers, Dodji.