[Bug libstdc++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3

2023-03-12 Thread murugesandins at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 --- Comment #13 from Murugesan Nagarajan --- 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:

[Bug libstdc++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3

2023-03-12 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 --- Comment #12 from Jonathan Wakely --- (In reply to Murugesan Nagarajan from comment #10) > Hence sigabrt signal needs to be handler at libc.so.6 Library Stop trying to "handle" the error and FIX IT. The error is that you didn't link to

[Bug libstdc++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3

2023-03-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 --- Comment #11 from Andrew Pinski --- (In reply to Murugesan Nagarajan from comment #10) > (In reply to Murugesan Nagarajan from comment #9) > > Thank you again. Reason for Porting this comment: > > Libc Library having core dump issue.hence

[Bug libstdc++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3

2023-03-10 Thread murugesandins at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 --- Comment #10 from Murugesan Nagarajan --- (In reply to Murugesan Nagarajan from comment #9) > Thank you again. Reason for Porting this comment: > Libc Library having core dump issue.hence thought of sharing this bug at > Libc Library. Hence

[Bug libstdc++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3

2023-03-10 Thread murugesandins at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 --- Comment #9 from Murugesan Nagarajan --- Thank you again. Reason for Porting this comment: Libc Library having core dump issue.hence thought of sharing this bug at Libc Library.

[Bug libstdc++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3

2023-03-10 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 --- Comment #8 from Jonathan Wakely --- 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.

[Bug libstdc++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3

2023-03-09 Thread murugesandins at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 --- Comment #7 from Murugesan Nagarajan --- (In reply to Andrew Pinski from comment #3) > The reason for the abort is because you didn't catch the exception as > libstc++ is throwing one because threads are not enabled at runtime via the >

[Bug libstdc++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3

2023-03-09 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 --- Comment #6 from Andrew Pinski --- > what(): Enable multithreading to use std::thread: It explicitly says what needs to be done. And to enable multithreading on gnu/Linux you use -pthread option or link against libpthread. Newer gnu/Linux

[Bug libstdc++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3

2023-03-09 Thread murugesandins at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 --- Comment #5 from Murugesan Nagarajan --- (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. >

[Bug libstdc++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3

2023-03-09 Thread murugesandins at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 --- Comment #4 from Murugesan Nagarajan --- 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