Bernhard Reutner-Fischer wrote:
Any chance that the c99-ldbl-math.patch
does not fix the problem ?
You may need to recompile your app. Note that isinf is a macro,
so if you get errors about this _symbol_ not being found then
there is something odd going on.
Since you didn't paste the
Rob Landley wrote:
Could you post your simple test program? I tried to come up with one
(attached), built it with:
i686-gcc thread-hello2.c -lpthread --static
And it worked exactly the same way on gcc and on uClibc (with svn 23784).
My uClibc .config is also attached.
My program
Rob Landley wrote:
On Tuesday 21 October 2008 01:47:48 Ming-Ching Tiew wrote:
Rob Landley wrote:
On Monday 20 October 2008 22:25:37 Ming-Ching Tiew wrote:
5. In the bugged case, the daemonized process did not
actually die, it lingers around ( it's one of the 3 processes
Rob Landley wrote:
On Monday 20 October 2008 22:25:37 Ming-Ching Tiew wrote:
5. In the bugged case, the daemonized process did not
actually die, it lingers around ( it's one of the 3 processes ).
Further down in the source, it calls ast_makesocket().
But in ast_makesocket
Rob Landley wrote:
Do you have a small test case that's not part of the asterisk
package but just a program we can compile and run on our own
systems?
I will try to write one to see if it is repeatable. I have heard
people having this problem with 'dropbear' but I have not seen it
Rob Landley wrote:
On Friday 17 October 2008 05:29:36 Bernhard Reutner-Fischer wrote:
On Fri, Oct 17, 2008 at 06:15:58PM +0800, Ming-Ching Tiew wrote:
I have been using asterisk ( eg 1.4.20.1 ) with uclibc-0.9.28 all
the while and it has been working.
But recently I feel
Rob Landley wrote:
Ok, it's sounding like a race condition in uClibc's current daemon()
implementation, triggered by the parent exiting before the child
finishes whatever it's doing in daemon().
However, it doesn't sound like the child process _dies_. Your
original bug report involved
Bernhard Reutner-Fischer wrote:
On Tue, Oct 14, 2008 at 12:42:31PM +0800, Ming-Ching Tiew wrote:
My app crashed in uClibc after running for about a week,
and this is the kernel dmesg log :-
6my_app[5656]: segfault at fea0 ip b743a437 sp 0818ff04
error 6 in libuClibc-0.9.28.so[b740e000
My app crashed in uClibc after running for about a week,
and this is the kernel dmesg log :-
6my_app[5656]: segfault at fea0 ip b743a437 sp 0818ff04
error 6 in libuClibc-0.9.28.so[b740e000+37000]
Is there any suggestions for giving additional clues to the
crash ( perhaps the function
