public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/106845] [13 Regression] ICE in exceeds_p, at analyzer/store.cc:464 since r13-2029-g7e3b45befdbbf1a1
Date: Tue, 06 Sep 2022 13:36:20 +0000	[thread overview]
Message-ID: <bug-106845-4-FhXF7am28f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106845-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845

--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Failing assertion here:

#1  0x00000000014df116 in ana::byte_range::exceeds_p (this=0x7fffffffbf80,
other=..., out_overhanging_byte_range=0x7fffffffbfc0)
    at ../../src/gcc/analyzer/store.cc:464
464           gcc_assert (size > 0);


(gdb) list
459         {
460           /* THIS definitely exceeds OTHER.  */
461           byte_offset_t start = MAX (get_start_byte_offset (),
462                                      other.get_next_byte_offset ());
463           byte_offset_t size = get_next_byte_offset () - start;
464           gcc_assert (size > 0);
465           out_overhanging_byte_range->m_start_byte_offset = start;
466           out_overhanging_byte_range->m_size_in_bytes = size;
467           return true;
468         }

where "this" and "other" are both empty, having 0 size:

(gdb) call this->dump()
bytes 1-0
(gdb) call other.dump()
bytes 0--1

due to the cst_capacity_tree in the region_model::check_region_bounds caller is
zero.

  parent reply	other threads:[~2022-09-06 13:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06  7:06 [Bug analyzer/106845] New: [13 Regression] ICE in exceeds_p, at analyzer/store.cc:464 asolokha at gmx dot com
2022-09-06  9:00 ` [Bug analyzer/106845] [13 Regression] ICE in exceeds_p, at analyzer/store.cc:464 since r13-2029-g7e3b45befdbbf1a1 marxin at gcc dot gnu.org
2022-09-06  9:24 ` rguenth at gcc dot gnu.org
2022-09-06 13:36 ` dmalcolm at gcc dot gnu.org [this message]
2022-09-06 15:18 ` tlange at gcc dot gnu.org
2022-09-06 15:23 ` dmalcolm at gcc dot gnu.org
2022-09-06 15:32 ` tlange at gcc dot gnu.org
2022-09-11 22:02 ` cvs-commit at gcc dot gnu.org
2022-09-11 22:11 ` tlange at gcc dot gnu.org

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-106845-4-FhXF7am28f@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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: link
Be 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).