[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43389: 28.0.50; Emacs memory leaks
From: |
Andreas Schwab |
Subject: |
bug#43389: 28.0.50; Emacs memory leaks |
Date: |
Tue, 10 Nov 2020 14:01:26 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
On Nov 10 2020, Michael Heerdegen wrote:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> You can call malloc_info (0, stdout) to see the state of the heap.
>
> Was that meant for me? If yes: where do I call this? gdb?
Yes, as long as you are not stopped inside malloc.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/11/09
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/11/09
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/11/09
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/09
- bug#43389: 28.0.50; Emacs memory leaks, Andreas Schwab, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks,
Andreas Schwab <=
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks, Michael Heerdegen, 2020/11/10
- bug#43389: 28.0.50; Emacs memory leaks, Eli Zaretskii, 2020/11/10