From: praveen ab <praveenasb@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Random Crash Observed while running program compiled with latest gcc
Date: Thu, 9 Feb 2023 16:26:05 +0530 [thread overview]
Message-ID: <CAFtRY14PEx9R0pB8VxtoLTKUJRqNMFKM5naqxhM57Lp27z+zXw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
Hi All,
We are upgrading the GCC version for our existing C/C++ project.
Earlier we were using gcc 5.4 and everything was working fine.(The
application works fine even with gcc 7.4)
When trying to build the application using gcc 8.1 and above we are
observing the random crashes mostly segmentation fault.
Any suggestions on how to debug this?
Right now I am trying the following:
Enabling the -Wall flag and trying to fix all the warnings
Using GDB to inspect memory location and variables.
Please Suggest anything else that needs to be checked?
--
*Thanks and Regards,*
*Praveen AB*
next reply other threads:[~2023-02-09 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 10:56 praveen ab [this message]
2023-02-09 10:59 ` Xi Ruoyao
2023-02-09 11:01 ` Arsen Arsenović
2023-02-09 17:45 ` praveen ab
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=CAFtRY14PEx9R0pB8VxtoLTKUJRqNMFKM5naqxhM57Lp27z+zXw@mail.gmail.com \
--to=praveenasb@gmail.com \
--cc=gcc-help@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).