Displaying 5 results from an estimated 5 matches for "___errno".
Did you mean:
__errno
2006 May 28
0
sigbus fault ?
...-> libc:sigaddset(0xffbfd594, 0xa, 0x0, 0x0)
/1@1: -> libc:sigvalid(0xa, 0x0, 0x0, 0x0)
/1@1: <- libc:sigvalid() = 1
/1@1: <- libc:sigaddset() = 0
/1: sigprocmask(SIG_SETMASK, 0xFFBFD594, 0x00000000) = 0
/1@1: -> libc:___errno(0x0, 0x0, 0x0, 0x0)
/1@1: <- libc:___errno() = 0xfee43664
/1@1: -> libc:time(0x0, 0x0, 0x0, 0x0)
...
And the same sort of thing in gdb:
(gdb) run
Starting program: /opt/Samba/samba-3.0.22-with-ADS/sbin/smbd
Program received signal SIGSEGV, Segmentation fault....
2006 May 28
1
sigbus fault?
...-> libc:sigaddset(0xffbfd594, 0xa, 0x0, 0x0)
/1@1: -> libc:sigvalid(0xa, 0x0, 0x0, 0x0)
/1@1: <- libc:sigvalid() = 1
/1@1: <- libc:sigaddset() = 0
/1: sigprocmask(SIG_SETMASK, 0xFFBFD594, 0x00000000) = 0
/1@1: -> libc:___errno(0x0, 0x0, 0x0, 0x0)
/1@1: <- libc:___errno() = 0xfee43664
/1@1: -> libc:time(0x0, 0x0, 0x0, 0x0)
...
And the same sort of thing in gdb:
(gdb) run
Starting program: /opt/Samba/samba-3.0.22-with-ADS/sbin/smbd
Program received signal SIGSEGV, Segmentation fault....
2008 Apr 28
4
Wineserver causing heavy CPU load
I am running Fedora 8 uname -r = 2.6.24.4-64.fc8 on my box with Wine 0.9.58. When I first installed it I noticed that my CPU usage jumped and stayed at 100% with wineserver taking > 85%. I killed the wineserver process and it dropped down, however it soon jumped back up when wineserver restarted itself. I then killed it again and all related processes and disabled it from starting as a damen
2001 Jun 22
0
Half-Life: Selected Mode is not supported by your card
...o
checking whether external symbols need an underscore prefix... no
checking whether assembler accepts .string... yes
checking whether we can build a GNU style ELF dll... yes
checking for reentrant libc: __errno_location... yes
checking for reentrant libc: __error... no
checking for reentrant libc: ___errno... no
checking for reentrant libc: __thr_errno... no
checking for reentrant libc: __errno... no
checking for reentrant X libraries... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for __libc_fork... yes
checking for _lwp_create... no
checking for clone... yes
checking...
2006 Jul 17
7
access to errno when using pid provider
I would like to know how to get access to errno when using pid provider to probe calls to
libc functions like fopen(). The built-in errno appears to be only for system calls. What I''d
like to be able to do is investigate where in an application I''m encountering EMFILE and
what the stack looks like at the time.
This message posted from opensolaris.org