[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] -Wl,-rpath not passed through?
From: |
Michael Matz |
Subject: |
Re: [Tinycc-devel] -Wl,-rpath not passed through? |
Date: |
Mon, 6 Jun 2016 19:25:51 +0200 (CEST) |
User-agent: |
Alpine 2.20 (LSU 67 2015-01-07) |
Hi,
On Mon, 6 Jun 2016, Steffen Nurpmeso wrote:
> Bäh!
> Take this one, please, the other one deleted an option.
> Ciao!
I think this leaks memory when opath contains a string already. pbuf is
allocated memory, you free the opath, copy pbuf into npath, but then leak
pbuf itself (it's not leaked when opath is NULL, then it's freed in the
next call as opath). valgrind should find it. Fix that and push to mob
I'd say.
Ciao,
Michael.
- [Tinycc-devel] -Wl,-rpath not passed through?, Steffen Nurpmeso, 2016/06/02
- Re: [Tinycc-devel] -Wl,-rpath not passed through?, Steffen Nurpmeso, 2016/06/04
- Re: [Tinycc-devel] -Wl,-rpath not passed through?, David Mertens, 2016/06/04
- Re: [Tinycc-devel] -Wl,-rpath not passed through?, Michael Matz, 2016/06/05
- Re: [Tinycc-devel] -Wl,-rpath not passed through?, Steffen Nurpmeso, 2016/06/06
- Re: [Tinycc-devel] -Wl,-rpath not passed through?, Steffen Nurpmeso, 2016/06/06
- Re: [Tinycc-devel] -Wl,-rpath not passed through?, Steffen Nurpmeso, 2016/06/06
- Re: [Tinycc-devel] -Wl,-rpath not passed through?,
Michael Matz <=
- Re: [Tinycc-devel] -Wl,-rpath not passed through?, Steffen Nurpmeso, 2016/06/06