[Bug c++/113211] Trying to initialize the tripwire database ends up with a SEGV if a uid cannot be found

2024-01-02 Thread alexis at m2osw dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113211 --- Comment #4 from Alexis Wilke --- Well, it could be a glibc issue, but the syntax: static thread_local unsigned _blocked = 0; is a compiler thing, right? Looking at ldd output, it is 100% static: $ ldd tripwire not a dynamic

[Bug c++/113211] New: Trying to initialize the tripwire database ends up with a SEGV if a uid cannot be found

2024-01-02 Thread alexis at m2osw dot com via Gcc-bugs
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: alexis at m2osw dot com Target Milestone: --- On some systems, when I install tripwire, it crashes. Now I have had the problem many times, so I decided to look

[Bug c++/86296] Creating a pointer class for a unique_ptr<>() deleter fails with optimizations

2018-06-29 Thread alexis at m2osw dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86296 --- Comment #5 from Alexis Wilke --- I tested again under Ubuntu 16.04 and 18.04. Most everything doesn't work right under 16.04. However, when I tested under 18.04, I got the same output as you. So I guess there were problems in 5.x that have

[Bug c++/86296] Creating a pointer class for a unique_ptr<>() deleter fails with optimizations

2018-06-25 Thread alexis at m2osw dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86296 --- Comment #3 from Alexis Wilke --- Okay, I understand and fixed my pointer class and its usage (i.e. I not have an "operator T () const" instead of "T & operator * ()" and I use "safe_fd.get()" instead of "*safe_fd"). However, as an FYI, I

[Bug c++/86296] New: Creating a pointer class for a unique_ptr<>() deleter fails with optimizations

2018-06-24 Thread alexis at m2osw dot com
verity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: alexis at m2osw dot com Target Milestone: --- Created attachment 44317 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44317=edit Source exhibiting the

[Bug c++/61312] New: variable function parameters declared as const in the class may not be declared as const in the function definition

2014-05-25 Thread alexis at m2osw dot com
: 4.8.1 Status: UNCONFIRMED Severity: major Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: alexis at m2osw dot com In the following code, the functions test() and foo() are both declared with a flags parameter

[Bug c++/61312] variable function parameters declared as const in the class may not be declared as const in the function definition

2014-05-25 Thread alexis at m2osw dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61312 --- Comment #3 from Alexis Wilke alexis at m2osw dot com --- Wow! I see that is now... normal behavior. If you ask me, it sucks. But well... I suppose I don't count. Thank you for the PDF reference.

[Bug ada/51691] New: Cast of an array with type generates a please file bug message (See below)

2011-12-28 Thread alexis at m2osw dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51691 Bug #: 51691 Summary: Cast of an array with type generates a please file bug message (See below) Classification: Unclassified Product: gcc Version: 4.4.5 Status: