public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb: add missing nullptr checks in bpstat_check_breakpoint_conditions Date: Thu, 6 Oct 2022 09:37:52 +0000 (GMT) [thread overview] Message-ID: <20221006093752.105DF384B807@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=80e0c6dc91f52fad32c3ff3cf20da889d77013ac commit 80e0c6dc91f52fad32c3ff3cf20da889d77013ac Author: Andrew Burgess <aburgess@redhat.com> Date: Thu Oct 6 09:35:18 2022 +0100 gdb: add missing nullptr checks in bpstat_check_breakpoint_conditions Add a couple of missing nullptr checks in the function bpstat_check_breakpoint_conditions. No user visible change after this commit. Diff: --- gdb/breakpoint.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c index 29a02945234..a3a154c19a9 100644 --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c @@ -5358,7 +5358,7 @@ bpstat_check_breakpoint_conditions (bpstat *bs, thread_info *thread) else cond = bl->cond.get (); - if (cond && b->disposition != disp_del_at_next_stop) + if (cond != nullptr && b->disposition != disp_del_at_next_stop) { int within_current_scope = 1; struct watchpoint * w; @@ -5430,7 +5430,7 @@ bpstat_check_breakpoint_conditions (bpstat *bs, thread_info *thread) value_free_to_mark (mark); } - if (cond && !condition_result) + if (cond != nullptr && !condition_result) { infrun_debug_printf ("condition_result = false, not stopping"); bs->stop = 0;
reply other threads:[~2022-10-06 9:37 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221006093752.105DF384B807@sourceware.org \ --to=aburgess@sourceware.org \ --cc=gdb-cvs@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).