From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jan.kratochvil@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc patch] nomem: internal_error -> error
Date: Tue, 01 Jun 2010 17:56:00 -0000 [thread overview]
Message-ID: <201006011755.o51HtepM012252@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20100601164808.GA22487@host0.dyn.jankratochvil.net> (message from Jan Kratochvil on Tue, 1 Jun 2010 18:48:08 +0200)
> Date: Tue, 1 Jun 2010 18:48:08 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Hi,
>
> unfortunately I see this problem reproducible only with the
> archer-jankratochvil-vla branch (VLA = Variable Length Arrays - char[var]).
> OTOH this branch I hopefully submit in some form for FSF GDB later.
>
> In this case (a general problem but tested for example on Fedora 13 i686):
>
> int
> main (int argc, char **argv)
> {
> char a[argc];
> return a[0];
> }
>
> (gdb) start
> (gdb) print a
> ../../gdb/utils.c:1251: internal-error: virtual memory exhausted: can't allocate 4294951689 bytes.
>
> I find simple error as a perfectly reasonable there.
I disagree; this internal-error really is a bug in GDB. We should
never try to allocate that much memory.
next prev parent reply other threads:[~2010-06-01 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 16:48 Jan Kratochvil
2010-06-01 17:56 ` Mark Kettenis [this message]
2010-06-01 17:58 ` Jan Kratochvil
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=201006011755.o51HtepM012252@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox