Date: Thu, 29 Jan 2009 00:03:41 +0100 From: Christoph Mallon <christoph.mallon@gmx.de> To: Channa <channa.kad@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk Message-ID: <4980E44D.1040604@gmx.de> In-Reply-To: <515c64960901280437hd4f7b2dx36a1774afe2f5646@mail.gmail.com> References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> <E1LS9Pa-000NBW-Ct@kabab.cs.huji.ac.il> <515c64960901280425y642a190ka31409cfc2a2fd8f@mail.gmail.com> <49804FCE.7090405@gmx.de> <515c64960901280437hd4f7b2dx36a1774afe2f5646@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Channa schrieb: > Hi, > Thanks for the reply. > Does the same behaviour seen on FreeBSD environment? > I am using FreeBSD libraries to test the test code. > > So according to you its better to NULL terminate in the test code to avoid > this undefined behaviour? You have to avoid undefined behaviour. The moment you cause undefined behaviour the game is over. BTW: The character is named NUL. NULL is the name of the symbolic null pointer constant.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4980E44D.1040604>