public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "menkaur at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107034] New: SIGSEGV in code using c style array
Date: Sun, 25 Sep 2022 20:47:11 +0000 [thread overview]
Message-ID: <bug-107034-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107034
Bug ID: 107034
Summary: SIGSEGV in code using c style array
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: menkaur at gmail dot com
Target Milestone: ---
Created attachment 53625
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53625&action=edit
c++ code to reproduce the bug
Attached code will result in address boundary error or similar issues at the
first line in any method that contains it.
To get it to work, run `g++ -O0 main.cpp -o test && ./test`
I had a bug where I was passing arguments into method that contained similar
code, and, when examined in gdb, I was passing valid arguments and receiving
invalid arguments inside.
Bug only became apparent to me when using large enough array
next reply other threads:[~2022-09-25 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 20:47 menkaur at gmail dot com [this message]
2022-09-25 21:07 ` [Bug c++/107034] " pinskia at gcc dot gnu.org
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=bug-107034-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: link
Be 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).