From: "Quesada Gonzalez, Elena" <elena.quesada_gonzalez@siemens.com>
To: Rich Felker <dalias@libc.org>
Cc: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: RE: [musl] SIGSEV error when using REGEX with musl library
Date: Fri, 26 Nov 2021 11:46:25 +0000 [thread overview]
Message-ID: <DB8PR10MB32595A48B26D8BA81C21FC8FB5639@DB8PR10MB3259.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20211125155200.GB7074@brightrain.aerifal.cx>
Hi,
A simple main with the following code, should replicate the error.
#include <regex>
void main()
{
std::regex regexp("^[a-z0-9]{1,8}$");
std::string s = ("0xAz10145274");
if (false == std::regex_search(s, regexp))
{
// Only fatal. Statement is not initialized yet.
printf("Invalid regex [%s]\n", __FUNCTION__);
exit(1);
}
else {
printf("Regex ok [%s]\n", __FUNCTION__);
}
}
Thanks for your time
-----Mensaje original-----
De: Rich Felker <dalias@libc.org>
Enviado el: jueves, 25 de noviembre de 2021 16:52
Para: Quesada Gonzalez, Elena (SMO RI R&D ES PF 1) <elena.quesada_gonzalez@siemens.com>
CC: musl@lists.openwall.com
Asunto: Re: [musl] SIGSEV error when using REGEX with musl library
On Thu, Nov 25, 2021 at 02:53:13PM +0000, Quesada Gonzalez, Elena wrote:
> I have the following function that works fine if the regular expression is correct, but get a SIGSEGV when calling regex_search compiling with clang-9 and using musl 1.2.
> However, it works fine with glibc,
>
> Could be a bug in musl library?
>
>
> Find code below
>
> void CRuntimeCommandLine::LoadComplement(const multimap<std::string,
> std::string>& mapArguments) {
> // Find parameter
> multimap<string, string>::const_iterator iter;
> iter = mapArguments.find("Complement");
> if(iter == mapArguments.end())
> {
> // Only fatal. Statement is not initialized yet.
> Logger::fatal(Errors::RCMD_F005_MISSING_MANDATORY_PARAM, "Missing mandatory parameter --Complement");
> }
> // regex expression for system_secret to be checked (Max 4Bytes, hexadecimal number in lowe case letters and no 0x format)
> regex regexp("^[0-9a-f]{1,8}$");
>
> // regex_search that searches pattern regexp in the string mystr
> std::string s = iter->second.c_str();
> if (false == std::regex_search(s, regexp))
> {
> // Only fatal. Statement is not initialized yet.
> Logger::fatal(Errors::RCMD_F006_INVALID_VALUE, "Invalid --Complement=hexvalue value");
> }
> else
> {
> // get hexadecimal value
> (void)sscanf(s.c_str(), "%X", &(m_cmdParameters.complementValue));
> }
>
> }
> With kind regards
> Elena Quesada Gonzalez
Do you have a complete minimal-ish test case that can be compiled and show the same thing happening? Even just a dummy main() to call the above the way you expect it to be called?
Rich
next prev parent reply other threads:[~2021-11-26 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 14:53 Quesada Gonzalez, Elena
2021-11-25 15:52 ` Rich Felker
2021-11-26 11:46 ` Quesada Gonzalez, Elena [this message]
2021-11-26 16:32 ` Alex Xu
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=DB8PR10MB32595A48B26D8BA81C21FC8FB5639@DB8PR10MB3259.EURPRD10.PROD.OUTLOOK.COM \
--to=elena.quesada_gonzalez@siemens.com \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).