Bug#700738: valgrind summary

2013-03-09 Thread Thorsten Glaser
Sebastian Ramacher dixit: >Anyway, signals intermixed with ncurses is very much out of my comfort >zone. Maybe Thorsten (CCed) can provide additional input on those issues. Sorry, no, no practical experience either way, but it did raise all alarm bells here while reading it. bye, //mirabilos --

Bug#700738: valgrind summary

2013-03-09 Thread Sebastian Ramacher
On 2013-03-08 22:25:46, Antoine Beaupré wrote: > I really wonder what to do at this point. I can certainly upload the 2.0 > version to experimental to allow people to test this more thoroughly > (but then again, it's just once C file, easy enough to test). But I > don't feel those bugs are serious

Bug#700738: valgrind summary

2013-03-08 Thread Antoine Beaupré
On 2013-03-08, Sebastian Ramacher wrote: > On 2013-03-06 20:02:16, Antoine Beaupré wrote: >> So I ran the patched version under valgrind, which I am not familiar >> with at all so YMMV. >> >> I attach the output. >> >> Basically, what I see is one of those: >> >> ==3852== Conditional jump or mov

Bug#700738: valgrind summary

2013-03-08 Thread Sebastian Ramacher
On 2013-03-06 20:02:16, Antoine Beaupré wrote: > So I ran the patched version under valgrind, which I am not familiar > with at all so YMMV. > > I attach the output. > > Basically, what I see is one of those: > > ==3852== Conditional jump or move depends on uninitialised value(s) > ==3852== Use

Bug#700738: valgrind summary

2013-03-06 Thread Antoine Beaupré
So I ran the patched version under valgrind, which I am not familiar with at all so YMMV. I attach the output. Basically, what I see is one of those: ==3852== Conditional jump or move depends on uninitialised value(s) ==3852== Use of uninitialised value of size 8 ==3852== Syscall param rt_sigact