public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/26096] gdb sets breakpoint at cold clone Date: Tue, 09 Jun 2020 13:17:32 +0000 [thread overview] Message-ID: <bug-26096-4717-jHOjFUOR44@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26096-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26096 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- Tentative patch: ... diff --git a/gdb/utils.c b/gdb/utils.c index 102db28787..073d5b2e10 100644 --- a/gdb/utils.c +++ b/gdb/utils.c @@ -2652,7 +2652,18 @@ strncmp_iw_with_mode (const char *string1, const char *string2, return 0; } else - return (*string1 != '\0' && *string1 != '('); + { + if (*string1 == '\0') + return 0; + + if (*string1 == '(') + { + const char *end_str1 = string1 + strlen (string1); + return end_str1[-1] != ')'; + } + + return 1; + } } else return 1; ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-09 13:17 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-09 10:57 [Bug breakpoints/26096] New: " vries at gcc dot gnu.org 2020-06-09 13:17 ` vries at gcc dot gnu.org [this message] 2020-06-09 14:23 ` [Bug breakpoints/26096] " vries at gcc dot gnu.org 2021-05-29 10:38 ` vries at gcc dot gnu.org 2021-05-31 14:16 ` vries at gcc dot gnu.org 2021-05-31 14:35 ` vries at gcc dot gnu.org 2021-05-31 17:06 ` bernd.edlinger at hotmail dot de 2021-06-01 13:25 ` cvs-commit at gcc dot gnu.org 2021-06-01 13:33 ` vries at gcc dot gnu.org 2021-06-01 13:33 ` vries at gcc dot gnu.org 2021-06-01 14:14 ` bernd.edlinger at hotmail dot de
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-26096-4717-jHOjFUOR44@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).