From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21130 invoked by alias); 28 Jan 2002 17:33:01 -0000 Mailing-List: contact insight-prs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-prs-owner@sources.redhat.com Received: (qmail 21115 invoked by uid 71); 28 Jan 2002 17:33:00 -0000 Resent-Date: 28 Jan 2002 17:33:00 -0000 Resent-Message-ID: <20020128173300.21114.qmail@sources.redhat.com> Resent-From: insight-gnats@sources.redhat.com (GNATS Filer) Resent-To: nobody@sources.redhat.com Resent-Cc: insight-prs@sources.redhat.com Resent-Reply-To: insight-gnats@sources.redhat.com, Douglas.Swanson@compaq.com Received:(qmail 17573 invoked by uid 61); 28 Jan 2002 17:27:10 -0000 Message-Id:<20020128172710.17572.qmail@sources.redhat.com> Date: Mon, 28 Jan 2002 09:33:00 -0000 From: Douglas.Swanson@compaq.com Reply-To: Douglas.Swanson@compaq.com To: insight-gnats@sources.redhat.com X-Send-Pr-Version:gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: insight/123: Stepping into a void function and then Finishing it causes Insight to malfunction X-SW-Source: 2002-q1/txt/msg00060.txt.bz2 List-Id: >Number: 123 >Category: insight >Synopsis: Stepping into a void function and then Finishing it causes Insight to malfunction >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jan 28 09:33:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Douglas.Swanson@compaq.com >Release: unknown-1.0 >Organization: >Environment: Win2K / MinGW 2.95.3 / Gdb 5 / Insight >Description: I attach a small program that illustrates the failure. In a Dos window I compile this program with MinGW (2.95.3). I invoke Insight and step into (s) update(). After a few iterations of the nested "for" loops I finish (f) update(). Insight correctly highlights the invocation in main(), but now if I try to continue (c) nothing happens. I have a larger program from which this small example was derived. In that program after Insight returns to the invocation of update() subsequent next (n) commands provoke the following dialog box. Warning Program received signal SIGSEGV, Segmentation fault. Note: 1) Running the same executable under native gdb does not provoke this problem. 2) If I do not step into (s) the void function and finish (f) it, the problem does not occur. >How-To-Repeat: Please see Description >Fix: >Release-Note: >Audit-Trail: >Unformatted: