[uae] Re: bsdsocket emu issue
- From: Richard Drummond <evilrich@xxxxxxxxxxxxxx>
- To: uae@xxxxxxxxxxxxx
- Date: Tue, 14 Sep 2004 08:05:58 -0500
Hi Giorgio
On Monday 13 September 2004 12:48 pm, SukkoPera wrote:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 15442)]
> 0x405a7b41 in __errno_location () from /lib/libc.so.6
> (gdb) info stack
> #0 0x405a7b41 in __errno_location () from /lib/libc.so.6
> #1 0x405da354 in vfprintf () from /lib/libc.so.6
> #2 0x08106da0 in write_log_standard ()
> (gdb) c
> Continuing.
>
> [SNIP]
>
> isn't that weird?
Isn't it just? Hehe.
Yes. That's the sort of thing I was experiencing: inexplicable faults from
glibc.
I'm fairly sure it's a kernel configuration or glibc issue regarding threads.
But what precisely is causing it, I've no idea.
When I have some more time I'm going to try and write a more portable
implementation of the stack magic stuff which doesn't manually monkey about
with the stack. Maybe that will prove more robust.
Cheers,
Rich
Other related posts: