public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: alainc__@hotmail.com To: gcc-gnats@gcc.gnu.org Subject: c++/6805: Stack mess up with overloading a function... Date: Fri, 24 May 2002 18:26:00 -0000 [thread overview] Message-ID: <20020524225319.26623.qmail@sources.redhat.com> (raw) >Number: 6805 >Category: c++ >Synopsis: Stack mess up with overloading a function... >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Fri May 24 15:56:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Stack index defect >Release: unknown-2.95.3 >Organization: >Environment: Linux K6 200mhz kernel 2.2.17 >Description: When you trie to call overload a constructor function like: ACLASS::ACLASS() { ...some code here... } ACLASS::ACLASS(int something) { ...some code here... AFUNCTION(); ...some code here... } the code generated by gcc mess up the stack and call an other function. >How-To-Repeat: >Fix: The idea to avoid that trouble is to create a function that contain the code tant we want to share. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-24 22:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-24 18:26 alainc__ [this message] 2002-06-05 7:20 lerdsuwa 2003-01-01 18:27 neroden
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=20020524225319.26623.qmail@sources.redhat.com \ --to=alainc__@hotmail.com \ --cc=gcc-gnats@gcc.gnu.org \ /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).