Re: apparent 4 GB memory limit for brk() in solaris 8 on some hardware...?
From: Paul Pluzhnikov (ppluzhnikov-nsp_at_charter.net)
Date: 07/29/05
- Next message: Maxim Yegorushkin: "Re: socket select send"
- Previous message: clsmyth_at_fuzzy-elves.org: "Re: apparent 4 GB memory limit for brk() in solaris 8 on some hardware...?"
- In reply to: clsmyth_at_fuzzy-elves.org: "Re: apparent 4 GB memory limit for brk() in solaris 8 on some hardware...?"
- Next in thread: Stefaan A Eeckels: "Re: apparent 4 GB memory limit for brk() in solaris 8 on some hardware...?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 29 Jul 2005 09:21:16 -0700
clsmyth@fuzzy-elves.org writes:
> 1/a) I don't want to run truss wide open (too much data), so I guess I
> will specify memory-allocation-related syscalls only. With that in
> mind, I will probably run this truss command:
>
> truss -t brk,mmap -u malloc -o outfile -f -p pid
Truss is unlikely to reveal anything -- your pmap output (assuming
it was taken just before the failure) shows *nothing* that would
have prevented further brk() growth.
One other suggestion: try running the app with libmapmalloc (via
LD_PRELOAD) -- it may be able to bypass whatever limit you are
bumping into, or at least provide further clues.
Cheers,
-- In order to understand recursion you must first understand recursion. Remove /-nsp/ for email.
- Next message: Maxim Yegorushkin: "Re: socket select send"
- Previous message: clsmyth_at_fuzzy-elves.org: "Re: apparent 4 GB memory limit for brk() in solaris 8 on some hardware...?"
- In reply to: clsmyth_at_fuzzy-elves.org: "Re: apparent 4 GB memory limit for brk() in solaris 8 on some hardware...?"
- Next in thread: Stefaan A Eeckels: "Re: apparent 4 GB memory limit for brk() in solaris 8 on some hardware...?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]