[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 92071] Reading debugging info uses too much memory
From:       Julian Seward <jseward () acm ! org>
Date:       2005-08-26 0:48:44
Message-ID: 20050826004844.22305.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=92071         




------- Additional Comments From jseward acm org  2005-08-26 02:48 -------
> size of file is 186590057
> mmap failed, error is: Cannot allocate memory
> [...]
> +    if (oimage == ((Addr)(-1))) {
> +       perror ("mmap failed, error is");
> +       printf ("will try malloc + read\n");


That's not an unreasonable thing to try.  But it hides the
real problem.  Why would mmap of a 186M file fail soon after
startup (when not much memory is in use) ?  Something is screwy
in the address space management.
[prev in list] [next in list] [prev in thread] [next in thread]