Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc patch] nomem: internal_error -> error
Date: Tue, 01 Jun 2010 17:58:00 -0000	[thread overview]
Message-ID: <20100601175808.GA28301@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <201006011755.o51HtepM012252@glazunov.sibelius.xs4all.nl>

On Tue, 01 Jun 2010 19:55:40 +0200, Mark Kettenis wrote:
> > (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.

So that even if the object is really so large in the inferior GDB should be
fixed to read+process the object in multiple parts?  That makes sense.


Thanks,
Jan


      reply	other threads:[~2010-06-01 17:58 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
2010-06-01 17:58   ` Jan Kratochvil [this message]

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=20100601175808.GA28301@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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