Received: from cogitri.dev (cogitri.dev [207.180.226.74])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 49DB2782BAF
	for <~alpine/devel@lists.alpinelinux.org>; Sat,  5 Jun 2021 12:13:44 +0000 (UTC)
Message-ID: <5155d9c837fec2af2cdfc0bd48e24fc92a32618f.camel@cogitri.dev>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cogitri.dev; s=mail;
	t=1622895223; bh=IuR1Nw6vo+g6ehxXAvNmxVhPWWApaI/IPCgQ9Su1CG8=;
	h=Subject:From:To:In-Reply-To:References;
	b=nGnc9k4UStS8VHNc1+6OV9pJojrJRKxiEKZSrTPBuL5TpHWM5kCn6AeEuZUtuwLFa
	 Yn//Rfg0mjpVhI5pjU3n71dmxRVQRg/2OAv3z4UfWF8hiR1Y6Dqo7SbwUTNYTQHqlz
	 268k4TPoJG1uVxllad4O6Edf/GgPaqVA/Iy1hbwtuBOKq5L5BUebaWtKw6ZUrX6Nsm
	 qJuaJlXd7vlksXW5uxnELgMCAcHNkfE69mkX0OcMr045DLxvD/ljxLVA2RYLJHBo0c
	 w8eSSmGenn+8A7Hk03uFgoj/Dhfuxzx2ObVLBid8lgIDLzkl4c6IdFXDCvLM08C6/i
	 55Wr/DfYlvJqA==
Subject: Re: Debugging memory leaks in applications running on Alpine Linux
 + musl-libc
From: Rasmus Thomsen <oss@cogitri.dev>
To: Srinivasan J <srinidpdk@gmail.com>, ~alpine/devel@lists.alpinelinux.org
Date: Sat, 05 Jun 2021 14:13:37 +0200
In-Reply-To: <CAEbeQ+rLEBTenj_a1F+Xf3X-Efh0pizMGd_Au0jsOKK061i8xQ@mail.gmail.com>
References: 
	<CAEbeQ+rLEBTenj_a1F+Xf3X-Efh0pizMGd_Au0jsOKK061i8xQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256";
	protocol="application/pgp-signature"; boundary="=-VhCEWUS2ANzGkd4bl9DU"
Mime-Version: 1.0


--=-VhCEWUS2ANzGkd4bl9DU
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, 2021-06-05 at 17:14 +0530, Srinivasan J wrote:
> Hi,
> =C2=A0=C2=A0=C2=A0 Please share any experience with tools used to debug m=
emory leaks
> in Alpine Linux based dockers. I'm able to get a core, but none of
> the
> tools like memleax, VMware chap etc would work. I tried jemalloc, but
> even that doesn't work in Alpine Linux 3.11.11/3.13.5. Using valgrind
> is not an option in production environment.
>=20
> Regards,
> Srini


Hej,

I think clang's sanitizers (LSAN) should work once we bump clang to
12.x.x (which we can do after 3.14 got branched). In the meantime I
think Valgrind in an isolated environment is probably a better idea
(using other sanitizers in production isn't necessarily a good idea
either).

Regards,

Rasmus Thomsen

--=-VhCEWUS2ANzGkd4bl9DU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEErepJabCshwIJ3OXBERUkFRgVTqYFAmC7anEACgkQERUkFRgV
TqapexAAopT3pAnyAba1xSSx71y60hf3teC4cIVXyfFZ8jAZYWufIOKMU13KB++h
kY/61LeLstvEjHB6w+c5/Zx3uCaTeGIAAkP3ZGXx6egzHLzWGteIF9g04H1bzfcJ
/yi6Z6tbHLReFEk+ail1QNbfusGxfW5aj7SiuI5um1Nq5TkgTLNCPLVfW0oUv5YV
EATyFapv94/2Kd8DzBubCmS8Ibk6Fjtr1r1iI0ekMNgY0pYxfZ5YqZHN9qQoX80x
RFim4pVo2KMoDztzYsljuM0SNnRRR38TV15PiZTdE2Ibj7RGtqPTnEVT2cAvaER+
Vh13gBa9Iqkb0zksFm1FTQcQ6wh2To3Qku/A4FHMHMjmxiV6d9ezlnGMBdUElnFv
v77HVk9J7InweP4CrSuTkYR2g2tRywz/ibFpexm16Tgg/lHMltJAhV3zidzVLBDi
3y0YSeATvvKWHwf6TeDIrRCMSTYBBXLhLnPu+HTOXb2jac9DjHd8syvROzAAQT8l
sW0vC/eIIin5VNJgUoB+QoVR+Qy6aufhS9WHe9QMU11Z66PikDGjdqLNfH5QTnoN
MO2EIcAZIHQCL07eBoHPOydNdBfvIFFgQMPiR8bOQyo2oaazEpRcsS927uAeZ06i
fd47uBfJ0vTbu0XZdYSgVuLDDQeYR60py+YjxnueDK9dfoaBnoI=
=XL6p
-----END PGP SIGNATURE-----

--=-VhCEWUS2ANzGkd4bl9DU--