This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [rfc patch] nomem: internal_error -> error

From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
To: Mark Kettenis <mark dot kettenis at xs4all dot nl>
Cc: gdb-patches at sourceware dot org
Date: Tue, 1 Jun 2010 19:58:08 +0200
Subject: Re: [rfc patch] nomem: internal_error -> error
References: <20100601164808.GA22487@host0.dyn.jankratochvil.net> <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

References:
- [rfc patch] nomem: internal_error -> error
  - From: Jan Kratochvil
- Re: [rfc patch] nomem: internal_error -> error
  - From: Mark Kettenis

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]