Summary: | sys-apps/dbus-1.3.0-r1: dbus-daemon segfaults immediatly on x86-(open)solaris | ||
---|---|---|---|
Product: | Gentoo/Alt | Reporter: | Florian Ermisch <floh.edo> |
Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Solaris | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
output of "truss /opt/gentoo/usr/bin/dbus-daemon"
truss -flo $FILE $EPREFIX/dbus-daemon |
Description
Florian Ermisch
2010-04-01 11:56:57 UTC
Created attachment 226101 [details]
output of "truss /opt/gentoo/usr/bin/dbus-daemon"
looks like a thread/LWP-problem
[...]
getcontext(0x08046F1C)
getrlimit(RLIMIT_STACK, 0x08046F14) = 0
getpid() = 13318 [13314]
lwp_private(0, 1, 0xFEB82A00) = 0x000001C3
setustack(0xFEB82A60)
Incurred fault #6, FLTBOUNDS %pc = 0x00000000
siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
Received signal #11, SIGSEGV [default]
siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
[the end]
does truss -f give more information on what's happening? Created attachment 226619 [details]
truss -flo $FILE $EPREFIX/dbus-daemon
additional "-l" for showing light weight process IDs
don't think so, no forking, no LWPs created. "setustack getustack (2) - retrieve or change the address of per-LWP stack boundary information" says "These functions will fail if: EFAULT The spp or sp argument does not refer to a valid address." am I getting this wrong or is there a function with error handling segfaulting? dbus-1.3.0* has been removed from portage, it was only a prerelease please try dbus-1.4.0, and report if the problem persists |