On Sun, Jun 18, 2023 at 04:46:46PM +0200, Why 42? The lists account. wrote:
> Jun 18 16:18:23 mjoelnir mdnsd: startup
> Jun 18 16:18:23 mjoelnir mdnsd: fatal: bind: Address already in use
> Jun 18 16:23:02 mjoelnir mdnsd: startup
> Jun 18 16:23:02 mjoelnir mdnsd: fatal: bind: Address already in
On Sun, Jun 18, 2023 at 03:34:27PM +0200, Otto Moerbeek wrote:
> So what's in your malloc options?
Er, nothing:
mjoelnir:robb 18.06 15:57:29 [$?==1]# echo $MALLOC_OPTIONS
mjoelnir:robb 18.06 15:57:40 # echo $MALLOC_OPTIONS | cat -vet
$
mjoelnir:robb 18.06 15:59:25 [$?==1]# unset
On Sun, Jun 18, 2023 at 03:51:20PM +0200, Theo Buehler wrote:
> > So what's in your malloc options?
>
> mdnsd -d must have thrown this warning for nearly 7 years. With d, it sets
> 'malloc_options = "AFGJPX";'. You removed A and P end of october 2016.
Sigh should be "S".
I take care to
> So what's in your malloc options?
mdnsd -d must have thrown this warning for nearly 7 years. With d, it sets
'malloc_options = "AFGJPX";'. You removed A and P end of october 2016.
On Sun, Jun 18, 2023 at 03:24:17PM +0200, Why 42? The lists account. wrote:
>
> On Sun, Jun 04, 2023 at 01:03:14PM +0200, Otto Moerbeek wrote:
> > Hello,
> >
> > In the last few weeks a series of mallocs diff have been committed.
> > The last one today. That one allows malloc to detect more
On Sun, Jun 04, 2023 at 01:03:14PM +0200, Otto Moerbeek wrote:
> Hello,
>
> In the last few weeks a series of mallocs diff have been committed.
> The last one today. That one allows malloc to detect more cases of
> write-after-free. While that is a good thing, it might uncover latent
> bugs in
Hello,
In the last few weeks a series of mallocs diff have been committed.
The last one today. That one allows malloc to detect more cases of
write-after-free. While that is a good thing, it might uncover latent
bugs in appliations.
So if you are running current or snapshots, please keep an eye
