Re: mmap/munmap with zero length

so mmap differs from the POSIX recommendation right. the malloc.conf option seems more like a workaround/hack. imo it's confusing to have mmap und munmap deal differently with len=0. being able to succesfully alocate memory which cannot be removed doesn't seem logical to me. alex Nate Eldredge sc

'No buffer space available' messages from ral0 device

After I had 'wget' running for a while ral device became irresponsive and kept printing those messages: Jul 5 00:30:45 eagle dhcpcd[22608]: ral0: timed out Jul 5 00:30:45 eagle dhcpcd[22608]: ral0: lease expired 48949 seconds ago Jul 5 00:30:45 eagle dhcpcd[22608]: ral0: writev: No buffer spac

carriage return with stdout and stderr

i'm running something similar to this pseudo-code in an app of mine: for (i=0 ) fprintf(stdout,"TEXT %d\r", int); what's really strange is that if i print to stdout the output isn't very clean. the cursor jumps randomly within the output (being 1 line). if i print to stderr however the ou

Re: carriage return with stdout and stderr

On Sun, Jul 05, 2009 at 01:42:01PM +0200, Alexander Best wrote: > i'm running something similar to this pseudo-code in an app of mine: > for (i=0 ) > fprintf(stdout,"TEXT %d\r", int); > what's really strange is that if i print to stdout the output isn't very > clean. the cursor jumps rand

Re: carriage return with stdout and stderr

Alexander Best schrieb: i'm running something similar to this pseudo-code in an app of mine: for (i=0 ) fprintf(stdout,"TEXT %d\r", int); what's really strange is that if i print to stdout the output isn't very clean. the cursor jumps randomly within the output (being 1 line). if i prin

Re: carriage return with stdout and stderr

thanks. i remembered fprintf being buffered, but i always thought \r would also empty the buffer. now that explains everything. ;-) alex Jilles Tjoelker schrieb am 2009-07-05: > On Sun, Jul 05, 2009 at 01:42:01PM +0200, Alexander Best wrote: > > i'm running something similar to this pseudo-code i

Zero-length allocation with posix_memalign()

I recently submitted a patch to the vlc developers that prevents a crash on FreeBSD 8.0 by not calling posix_memalign() with a size argument of zero. A simplified test case would be: #include int main(int argc, char **argv) { void *ptr; posix_memalign(&ptr, 16, 0); return

Re: Zero-length allocation with posix_memalign()

Fabian Keil wrote: Rémi Denis-Courmont, one of the vlc developers, pointed out that passing a zero size to posix_memalign() should actually work, though: | In principle, while useless, there is no reason why allocating an empty | picture should not be possible. posix_memalign() does support zer

Re: Zero-length allocation with posix_memalign()

On 7/5/09, Fabian Keil wrote: > I recently submitted a patch to the vlc developers that prevents > a crash on FreeBSD 8.0 by not calling posix_memalign() with a > size argument of zero. > > A simplified test case would be: > > #include > int main(int argc, char **argv) { > void *ptr; >

Re: Problem with vm.pmap.shpgperproc and vm.pmap.pv_entry_max

On Fri, Jul 3, 2009 at 8:18 AM, c0re dumped wrote: > So, I never had problem with this server, but recently it starts to > giv me the following messages *every* minute : > > Jul 3 10:04:00 squid kernel: Approaching the limit on PV entries, > consider increasing either the vm.pmap.shpgperproc or