public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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: Fri, 10 Mar 2023 04:53:31 +0000 [thread overview]
Message-ID: <bug-109074-4-Z8F7u1RLIx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109074-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074
--- Comment #5 from Murugesan Nagarajan <murugesandins at gmail dot com> ---
(In reply to Murugesan Nagarajan from comment #4)
> Thank you for your comment.
> I feel that there WAS a bug in old libc library.
> I am not sure if current libc version having this bug or not.
> -----------------------------------------
> 01. external library /lib64/libc.so.6 => /lib64/libc-2.17.so
> $ /usr/bin/g++ -g -Wall libcversion.cpp -o ./a.out
> $ ./a.out
> GNU libc version: 2.17
> This should have been fixed in later versions of libc.
> I need to know related libc version without this bug 109074.
> -----------------------------------------
> 02. Bug related information from core file:
> $ /usr/bin/g++ -DLINUX -g -Wall thread.cpp -o ./a.out -std=c++11
> $ gdb a.out
> Reading symbols from /home/murugesan_openssl/a.out...done.
> (gdb) run
> Starting program: /home/murugesan_openssl/a.out
> terminate called after throwing an instance of 'std::system_error'
> what(): Enable multithreading to use std::thread: Operation not permitted
> Program received signal SIGABRT, Aborted.
> 0x00007ffff72311d7 in raise () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install
> glibc-2.17-157.el7.x86_64 libgcc-4.8.5-11.el7.x86_64
> libstdc++-4.8.5-11.el7.x86_64
> (gdb) where
> #0 0x00007ffff72311d7 in raise () from /lib64/libc.so.6
> #1 0x00007ffff72328c8 in abort () from /lib64/libc.so.6
> #2 0x00007ffff7b35ab5 in __gnu_cxx::__verbose_terminate_handler() () from
> /lib64/libstdc++.so.6
> #3 0x00007ffff7b33a26 in ?? () from /lib64/libstdc++.so.6
> #4 0x00007ffff7b33a53 in std::terminate() () from /lib64/libstdc++.so.6
> #5 0x00007ffff7b33c73 in __cxa_throw () from /lib64/libstdc++.so.6
> #6 0x00007ffff7b8a4b9 in
> std::thread::_M_start_thread(std::shared_ptr<std::thread::_Impl_base>) ()
> from /lib64/libstdc++.so.6
> #7 0x00000000004020d2 in std::thread::thread<void (&)()>
> (this=0x7fffffffdc90,
> __f=@0x4017cd: {void (void)} 0x4017cd <ThreadMethod()>) at
> /usr/include/c++/4.8.2/thread:135
> #8 0x0000000000401a89 in main () at thread.cpp:50
> (gdb)
> -----------------------------------------
Actually I am from India. wait for my reply(if required) on next day.
next prev parent reply other threads:[~2023-03-10 4:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 6:56 [Bug c++/109074] New: " murugesandins at gmail dot com
2023-03-09 10:20 ` [Bug c++/109074] " rguenth at gcc dot gnu.org
2023-03-09 11:28 ` pinskia at gcc dot gnu.org
2023-03-09 11:30 ` pinskia at gcc dot gnu.org
2023-03-10 4:34 ` [Bug libstdc++/109074] " murugesandins at gmail dot com
2023-03-10 4:53 ` murugesandins at gmail dot com [this message]
2023-03-10 5:01 ` pinskia at gcc dot gnu.org
2023-03-10 5:26 ` murugesandins at gmail dot com
2023-03-10 10:32 ` redi at gcc dot gnu.org
2023-03-10 21:30 ` murugesandins at gmail dot com
2023-03-10 23:20 ` murugesandins at gmail dot com
2023-03-10 23:30 ` pinskia at gcc dot gnu.org
2023-03-12 20:52 ` redi at gcc dot gnu.org
2023-03-13 3:30 ` murugesandins at gmail dot com
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-109074-4-Z8F7u1RLIx@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).