I think I've tracked down where the hang is occurring, using memprof
with glibc 2.3.5 on Linux 2.6.13.4 (though I don't undestand _why_
it's occurring).
The do_malloc function in memprof's libmemintercept calls
mi_call_with_backtrace(), which in turns calls the glibc function
backtrace(),
Allin Cottrell wrote:
I've successfully used memprof for leak-checking my app in the past, but
on trying it recently something odd happens: memprof starts up OK, and
it also starts up the target program, but the target program is not
visible (doesn't appear on screen) and memprof records no
On Tue, 25 Oct 2005, Olivier Sessink wrote:
Allin Cottrell wrote:
I've successfully used memprof for leak-checking my app in the past, but
on trying it recently something odd happens: memprof starts up OK, and
it also starts up the target program, but the target program is not
visible (doesn't
I've successfully used memprof for leak-checking my app in the past,
but on trying it recently something odd happens: memprof starts up
OK, and it also starts up the target program, but the target program
is not visible (doesn't appear on screen) and memprof records no
memory usage.
I tried
Allin Cottrell wrote:
I've successfully used memprof for leak-checking my app in the past,
but on trying it recently something odd happens: memprof starts up
OK, and it also starts up the target program, but the target program
is not visible (doesn't appear on screen) and memprof records
On Mon, 24 Oct 2005, Gus Koppel wrote:
Allin Cottrell wrote:
I've successfully used memprof for leak-checking my app in the past,
but on trying it recently something odd happens: memprof starts up
OK, and it also starts up the target program, but the target program
is not visible (doesn't
