Processed: Re: libc6-dev: mblen is erroneously marked warn_unused_result

Processing commands for cont...@bugs.debian.org: > tags 674917 + upstream patch Bug #674917 [libc6-dev] libc6-dev: mblen is erroneously marked warn_unused_result Added tag(s) upstream and patch. > quit Stopping processing here. Please contact me if you need assistance. -- 674917: http://bugs.de

Bug#674917: libc6-dev: mblen is erroneously marked warn_unused_result

tags 674917 + upstream patch quit Hi, Antti-Juhani Kaijanaho wrote: > However, so far as I can see, ignoring the return value of mblen is never a > security problem and is sometimes appropriate (the first call to the function > is often mblen(NULL, 0), the result value of which is usually of no

Re: Bug#672152: perl: FTBFS on kfreebsd-*: dist/threads-shared/t/waithires.t failing

On Sun, May 27, 2012 at 08:00:48PM +0100, Steven Chamberlain wrote: > On 27/05/12 17:55, Steven Chamberlain wrote: > > I just checked to see if Petr's eglibc getosreldate() fix made any > > difference to the Perl waithires.t test [...] > > Actually this is fixed (#673711), I just didn't notice the

Bug#674917: libc6-dev: mblen is erroneously marked warn_unused_result

On Tue, May 29, 2012 at 11:36:03AM -0500, Jonathan Nieder wrote: > This doesn't seem to be fixed upstream, so please report it to > , product glibc, component libc and > let us know the bug number so we can track it. It is commonly accepted Debian practice for the m

Bug#674917: libc6-dev: mblen is erroneously marked warn_unused_result

forwarded 674917 http://sourceware.org/PR14176 quit Antti-Juhani Kaijanaho wrote: > However, I've done what you asked. > http://sourceware.org/bugzilla/show_bug.cgi?id=14176 Thanks much. Kind regards, Jonathan -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject

Processed: Re: libc6-dev: mblen is erroneously marked warn_unused_result

Processing commands for cont...@bugs.debian.org: > forwarded 674917 http://sourceware.org/PR14176 Bug #674917 [libc6-dev] libc6-dev: mblen is erroneously marked warn_unused_result Set Bug forwarded-to-address to 'http://sourceware.org/PR14176'. > quit Stopping processing here. Please contact me

Bug#674917: libc6-dev: mblen is erroneously marked warn_unused_result

On Tue, May 29, 2012 at 11:36:03AM -0500, Jonathan Nieder wrote: > Using -Werror in contexts other than private development where you > control the toolchain and can easily suppress known warnings is not > very wise. I think it's a wise policy to tolerate no warnings to the extent possible. -Werro

Bug#673596: libc6: FTBFS on wheezy/sid amd64 (test suite failures)

I've been bitten by this bug too, and here is what I've gathered: tst-eintr1 spawns threads continuously, without joining them, until it receives a SIGALRM. This is supposed to occur take 3 seconds, which, on my computer, makes roughly 5k threads unjoined threads, which is already a large number

Bug#673596: libc6: FTBFS on wheezy/sid amd64 (test suite failures)

Hi Thibaut, Thibaut Girka wrote: > I've been bitten by this bug too, and here is what I've gathered: > > tst-eintr1 spawns threads continuously, without joining them, until it > receives a SIGALRM. Thanks for the analysis. If I am reading correctly, tst-eintr1 tries to spawn 11 child threads, o

Bug#673596: libc6: FTBFS on wheezy/sid amd64 (test suite failures)

On Tue, May 29, 2012 at 10:07:42PM -0500, Jonathan Nieder wrote: > Hi Thibaut, > > Thibaut Girka wrote: > > > I've been bitten by this bug too, and here is what I've gathered: > > > > tst-eintr1 spawns threads continuously, without joining them, until it > > receives a SIGALRM. > > Thanks for th