From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id E1FF23858D39; Mon, 13 Mar 2023 03:30:30 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E1FF23858D39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678678230;
	bh=9/zlNPTxhRozgPHRSW91Bd9jWLnf3q1DoBQKp+2GFGc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=N/UWTq4KJiTG0M1BVqLehDfpxF6azvCei+nXDvDfbsGQH2MfyC2LMkdav4URzxqS/
	 9RJ+pa2Ka6N9+wfz6pdIX+GfTHwoz3X65v0pmFiTOsJUMWdInL8hJ/YtIu4+ZMZRKP
	 Km48wF2jMcQYlVV5Ak3/01hbEABFQ1hakRsrWZ00=
From: "murugesandins at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109074] SIGABRT signal without using -lpthread at
 Linux RHEL 7.3
Date: Mon, 13 Mar 2023 03:30:29 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.8.5
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: murugesandins at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109074-4-DfrMxEXHMm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109074-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109074-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109074

--- Comment #13 from Murugesan Nagarajan <murugesandins at gmail dot com> -=
--
MY LAST COMMENT:
I agree.
Normally I used to handle bug fix using following ways:
1. Steps to reproduce to issue creating core dump files.
   There are some other ways which may work(Example: -pthread or
-lmurugesanopenssl or -lrfcsdk or -lnwrfcsdk or ... options)
After this I used to receive/send that test result to/from test/development
team.
Few libraries I faced a lot of errors during 2008 to 2013 and FEW of them(I
guess 4 out of six) were fixed during.
2. Hence I reported this error at current(old version) library. I agree tha=
t it
is working when we use -pthread.
However, this may report some other issue in future.=