From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13373 invoked by alias); 1 Aug 2003 07:06:53 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 13366 invoked from network); 1 Aug 2003 07:06:52 -0000 Received: from unknown (HELO vortex.servnow.com) (64.5.48.88) by sources.redhat.com with SMTP; 1 Aug 2003 07:06:52 -0000 Received: from adsl-67-123-57-211.dsl.lsan03.pacbell.net ([67.123.57.211] helo=tbird) by vortex.servnow.com with asmtp (Exim 3.36 #1) id 19iU0W-0001OR-00 for gdb@sources.redhat.com; Fri, 01 Aug 2003 03:07:20 -0400 Message-ID: <002101c357fb$7a516bb0$0200a8c0@tbird> From: "Robin Rowe" To: Subject: Single-step runaway Date: Fri, 01 Aug 2003 07:06:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vortex.servnow.com X-AntiAbuse: Original Domain - sources.redhat.com X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0] X-AntiAbuse: Sender Address Domain - movieeditor.com X-SW-Source: 2003-08/txt/msg00001.txt.bz2 I have a program that gdb doesn't seem to be able to enforce a breakpoint on. As I single step through my code gdb suddenly takes the bit in its teeth and slips away to run the program forward as though I had issued continue. When I reach a particular function call in my code it simply takes off and runs to completion (it's a batch process) rather than stepping into the call as it should. If I stepi half a dozen times I can get inside the call and single-stepping mostly works from there forward -- but not consistently so. As a debugger it is almost unusable with this flaw. It would be faster to use printf. Other gdb users tell me they have encountered erratic behaviour like this from time to time. Is this a known bug? Why is it happening? What can be done about it? FYI, there is nothing exotic about the function call that runs away. It is a statically linked library C call. That library uses C++ internally, but the interface is an extern "C" function call that passes a straight C struct. All the code involved is code I wrote myself and compiled at the same time. I'm running on RedHat 7.1. Tried compiling gdb 5.3 from source, but no difference. Suggestions? Thanks, Robin --------------------------------------------------------------------------- Robin.Rowe@MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software