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 300D73858C1F; Fri, 10 Mar 2023 10:32:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 300D73858C1F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678444375;
	bh=QfZ4G6Cr/dyiKfsGIS9SakW7J7JK/UX8BHLLWSD3xlI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=rH0MKwYZVnK/tY7CB5MTqO9YgcNqn+K8rtjlMl7d6q/CINfmoR0Dbq1cKO+sM45PJ
	 B9g8B/GDIvSa+Qrx4bcArgIkPNlf0U0B6oiBQ4+LS2DvrJ+phkUWiLQcOKIQhE0cUD
	 QasCyPuUWFmAq4vTkGjMLIiG4eqmB/PT9rSj/4mc=
From: "redi at gcc dot gnu.org" <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: Fri, 10 Mar 2023 10:32:53 +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: redi at gcc dot gnu.org
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-hVM3uDQQjM@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 #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
You need to use -pthread to use std::thread.

That's what the exception is telling you.

Catching the exception doesn't solve the problem.

Use -pthread.=