public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: Douglas.Swanson@compaq.com To: insight-gnats@sources.redhat.com Subject: insight/123: Stepping into a void function and then Finishing it causes Insight to malfunction Date: Mon, 28 Jan 2002 09:33:00 -0000 [thread overview] Message-ID: <20020128172710.17572.qmail@sources.redhat.com> (raw) >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:
next reply other threads:[~2002-01-28 17:33 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-28 9:33 Douglas.Swanson [this message] 2002-02-12 17:00 kseitz
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020128172710.17572.qmail@sources.redhat.com \ --to=douglas.swanson@compaq.com \ --cc=insight-gnats@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).