Re: insight/123: Stepping into a void function and then Finishing it causes Insight to malfunction

Re: insight/123: Stepping into a void function and then Finishing it causes Insight to malfunction

[kseitz]

Synopsis: Stepping into a void function and then Finishing it causes Insight to malfunction

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Tue Feb 12 17:00:52 2002
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->feedback
State-Changed-By: kseitz
State-Changed-When: Tue Feb 12 17:00:52 2002
State-Changed-Why:
    There appears to be some problem with the insight distributed with bloodshed.net's IDE. I've tried to reproduce this problem with mingw (just downloaded/installed) and Insight off the 5.1 branch (officially 5.1.1). I cannot reproduce the problem.
    
    I suggest either building your own 5.1.1 Insight from the sources (which I would support) or turning to Bloodshed for support, since they are distributing our code in binary to users.

http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=123

insight/123: Stepping into a void function and then Finishing it causes Insight to malfunction

[Douglas.Swanson]

>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: