public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "luis.machado at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/26362] [aarch64] gdb/utils.c:671: internal-error: virtual memory exhausted: can't allocate 187647121162241 bytes
Date: Wed, 12 Aug 2020 18:20:21 +0000	[thread overview]
Message-ID: <bug-26362-4717-8GhTHxYRfI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26362-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26362

--- Comment #19 from Luis Machado <luis.machado at linaro dot org> ---
I thought about that too.

The only way it would've bypassed the check is if length is less than or equal
to max_value_size. Is length cast to a signed integer when compared to
max_value_size (a signed int)?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-08-12 18:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 14:17 [Bug tdep/26362] New: " vries at gcc dot gnu.org
2020-08-10 14:18 ` [Bug tdep/26362] " vries at gcc dot gnu.org
2020-08-10 14:18 ` vries at gcc dot gnu.org
2020-08-10 14:26 ` [Bug tdep/26362] [aarch64] " vries at gcc dot gnu.org
2020-08-10 14:30 ` alahay01 at gcc dot gnu.org
2020-08-11 13:29 ` luis.machado at linaro dot org
2020-08-11 15:25 ` vries at gcc dot gnu.org
2020-08-11 19:38 ` luis.machado at linaro dot org
2020-08-12  7:50 ` vries at gcc dot gnu.org
2020-08-12  9:10 ` vries at gcc dot gnu.org
2020-08-12 12:19 ` vries at gcc dot gnu.org
2020-08-12 12:21 ` vries at gcc dot gnu.org
2020-08-12 12:31 ` vries at gcc dot gnu.org
2020-08-12 13:47 ` luis.machado at linaro dot org
2020-08-12 13:53 ` luis.machado at linaro dot org
2020-08-12 14:17 ` luis.machado at linaro dot org
2020-08-12 14:17 ` luis.machado at linaro dot org
2020-08-12 16:34 ` luis.machado at linaro dot org
2020-08-12 17:02 ` andrew.burgess at embecosm dot com
2020-08-12 17:17 ` luis.machado at linaro dot org
2020-08-12 17:23 ` vries at gcc dot gnu.org
2020-08-12 17:26 ` luis.machado at linaro dot org
2020-08-12 18:12 ` vries at gcc dot gnu.org
2020-08-12 18:20 ` luis.machado at linaro dot org [this message]
2020-08-12 18:32 ` luis.machado at linaro dot org
2020-08-12 19:06 ` luis.machado at linaro dot org
2020-08-12 21:13 ` vries at gcc dot gnu.org
2020-08-12 21:15 ` luis.machado at linaro dot org
2020-08-12 22:03 ` vries at gcc dot gnu.org
2020-08-12 22:19 ` luis.machado at linaro dot org
2020-08-14 15:46 ` vries at gcc dot gnu.org
2020-08-15 10:01 ` vries at gcc dot gnu.org
2020-08-15 10:05 ` vries 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-26362-4717-8GhTHxYRfI@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: 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).