This is the mail archive of the gdb-prs@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]

[Bug gdb/16277] gdb virtual memory exhausted


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

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |palves at redhat dot com

--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
Could you please try a more recent gdb?  (7.6.1 and also ideally, mainline). 
It's possible this is already fixed.

> gdb is crashing with error message virtual memory exhausted: can't allocate
> **** bytes.

The redacted number (****) is actually important.  E.g, 4294967295 would mean
something tried to allocate -1 bytes. [(unsigned)-1 == 4294967295].

Can you get a GDB backtrace?

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


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