public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: llewins@raytheon.com To: insight-gnats@sources.redhat.com Subject: insight/204: SEGV in __libtk80_a_iname Date: Fri, 10 Jan 2003 23:43:00 -0000 [thread overview] Message-ID: <20030110233635.12862.qmail@sources.redhat.com> (raw) >Number: 204 >Category: insight >Synopsis: SEGV in __libtk80_a_iname >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jan 10 15:43:00 PST 2003 >Closed-Date: >Last-Modified: >Originator: Lloyd J. Lewins >Release: cvs Jan 9, 2002 >Organization: >Environment: cygwin >Description: When debugging main.cc, moving the mouse over the statement: thisRoute->analyzeZD(); causes insight to crash with a SEGV. >How-To-Repeat: Set a break point on line 57. Run and then place the mouse on line 57. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="main.cc" Content-Disposition: inline; filename="main.cc" /* Submitted by: Lloyd Lewins, llewins@raytheon.com Cause insight to crash with SEGV Insight version: GNU gdb 2003-01-09-cvs gcc version: gcc version 2.95.3-5 (cygwin special) Compiled with -g option. When debugging main.cc, moving the mouse over the statement: thisRoute->analyzeZD(); causes insight to crash with a SEGV. Set a break point on line 57. Run and then place the mouse on line 57. The following is the error (captured by running insight within gdb): Program received signal SIGSEGV, Segmentation fault. 0x6108d57f in _libtk80_a_iname () */ #include <vector> class route { public: route(void) { } static void analyzeAllZD(void); class destination { public: destination(route* const nextRoute) : nextRoute(nextRoute) { } route* const nextRoute; }; typedef std::vector<destination*> destination_vector; void analyzeZD (void); destination_vector destinations; }; void route::analyzeZD(void) { } void route::analyzeAllZD(void) { route* thisRoute = new route(); thisRoute->analyzeZD(); } int main(void) { route::analyzeAllZD(); }
reply other threads:[~2003-01-10 23:43 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030110233635.12862.qmail@sources.redhat.com \ --to=llewins@raytheon.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).