public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/102918] New: Undefined behaviour in regex header (uininitialized boolean)
@ 2021-10-24 21:39 camilotalero96 at hotmail dot com
2021-10-25 8:48 ` [Bug libstdc++/102918] " redi at gcc dot gnu.org
2024-04-09 21:55 ` pinskia at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: camilotalero96 at hotmail dot com @ 2021-10-24 21:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102918
Bug ID: 102918
Summary: Undefined behaviour in regex header (uininitialized
boolean)
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: camilotalero96 at hotmail dot com
Target Milestone: ---
I am using undefined behaviour sanitizers and they are detecting a potential
bug in teh regex header, the specific report is:
`/usr/include/c++/11/bits/regex.h:909:15: runtime error: load of value 192,
which is not a valid value for type 'bool'`
Which does seem like the use of a potentially uninitialized boolean.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libstdc++/102918] Undefined behaviour in regex header (uininitialized boolean)
2021-10-24 21:39 [Bug c++/102918] New: Undefined behaviour in regex header (uininitialized boolean) camilotalero96 at hotmail dot com
@ 2021-10-25 8:48 ` redi at gcc dot gnu.org
2024-04-09 21:55 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2021-10-25 8:48 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102918
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2021-10-25
Status|UNCONFIRMED |WAITING
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
std::sub_match only has one constructor, and it initializes the bool. The only
stores to that variable are literal treu or false values, or the result of a
boolean expression first != last. So there's no way I can see for the library
to cause this behaviour Are you sure you're not causing undefined behaviour in
your own code?
Have you tried building with -D_GLIBCXX_DEBUG to get runtime checks in
std::match_results.
Without more details there's nothing we can do here. The <regex> code looks
correct.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libstdc++/102918] Undefined behaviour in regex header (uininitialized boolean)
2021-10-24 21:39 [Bug c++/102918] New: Undefined behaviour in regex header (uininitialized boolean) camilotalero96 at hotmail dot com
2021-10-25 8:48 ` [Bug libstdc++/102918] " redi at gcc dot gnu.org
@ 2024-04-09 21:55 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-04-09 21:55 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102918
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|WAITING |RESOLVED
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
No feedback or a testcase in over 2 years so closing as invalid. If you provide
a testcase we will be able to look into it but until then, closing as invalid.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-04-09 21:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-24 21:39 [Bug c++/102918] New: Undefined behaviour in regex header (uininitialized boolean) camilotalero96 at hotmail dot com
2021-10-25 8:48 ` [Bug libstdc++/102918] " redi at gcc dot gnu.org
2024-04-09 21:55 ` pinskia at gcc dot gnu.org
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).