This is the mail archive of the
mailing list for the Insight project.
insight/123: Stepping into a void function and then Finishing it causes Insight to malfunction
- From: Douglas dot Swanson at compaq dot com
- To: insight-gnats at sources dot redhat dot com
- Date: 28 Jan 2002 17:27:10 -0000
- Subject: insight/123: Stepping into a void function and then Finishing it causes Insight to malfunction
- Reply-to: Douglas dot Swanson at compaq dot com
>Synopsis: Stepping into a void function and then Finishing it causes Insight to malfunction
>Arrival-Date: Mon Jan 28 09:33:00 PST 2002
Win2K / MinGW 2.95.3 / Gdb 5 / Insight
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
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.
Program received signal SIGSEGV, Segmentation fault.
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.
Please see Description