[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dumper problems and a possible solutions
From: |
Dmitry Antipov |
Subject: |
Re: Dumper problems and a possible solutions |
Date: |
Wed, 25 Jun 2014 22:30:22 +0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 06/25/2014 10:08 PM, Rich Felker wrote:
Are there such objects that need to be preserved across dumping?
I don't know, and the worst thing is that we can't control over this.
With my debug build, 'ldd src/temacs | wc -l' shows 112 external
libraries. What if just one of these libraries uses malloc() to allocate
an internal object in __attribute__((constructor)) function? There is no
way to handle this except intercepting all malloc() calls. This way we
move to our own heap management, which will have the same heap parsability
issues like system's malloc(), etc.
Dmitry
- Re: Dumper problems and a possible solutions, (continued)
- Re: Dumper problems and a possible solutions, Dmitry Antipov, 2014/06/25
- Re: Dumper problems and a possible solutions, Rich Felker, 2014/06/26
- Re: Dumper problems and a possible solutions, Dmitry Antipov, 2014/06/26
- Re: Dumper problems and a possible solutions, Rich Felker, 2014/06/26
- Re: Dumper problems and a possible solutions, Eli Zaretskii, 2014/06/26
- Re: Dumper problems and a possible solutions, Rich Felker, 2014/06/26
- Re: Dumper problems and a possible solutions, Andreas Schwab, 2014/06/25
- Re: Dumper problems and a possible solutions, Samuel Bronson, 2014/06/25
- Re: Dumper problems and a possible solutions, Rich Felker, 2014/06/25
Re: Dumper problems and a possible solutions, Rich Felker, 2014/06/25
Re: Dumper problems and a possible solutions, Eli Zaretskii, 2014/06/25
Re: Dumper problems and a possible solutions, Stephen J. Turnbull, 2014/06/25
Re: Dumper problems and a possible solutions, Stefan Monnier, 2014/06/25