> I'd suggest truss/kdump/etc to try and figure out what avp is doing
> differently on -current then -stable.
>
Is anything obvious here? (If not, I won't persue the matter, but ask
Kaspersky nicely if they can make a Fbsd-5 version.
I know current is not for production; this is my testmachine.
The last 50 lines from kdump:
22194 AvpBSD CALL sigprocmask(0x3,0x280845f0,0)
22194 AvpBSD RET sigprocmask 0
22194 AvpBSD CALL readlink(0x281627f4,0xbfbff218,0x3f)
22194 AvpBSD NAMI "/etc/malloc.conf"
22194 AvpBSD RET readlink -1 errno 2 No such file or directory
22194 AvpBSD CALL mmap(0,0x1000,0x3,0x1002,0xffffffff,0,0,0)
22194 AvpBSD RET mmap 672641024/0x2817b000
22194 AvpBSD CALL break(0x8083000)
22194 AvpBSD RET break 0
22194 AvpBSD CALL break(0x8084000)
22194 AvpBSD RET break 0
22194 AvpBSD CALL sigaction(0xc,0xbfbff310,0xbfbff2f8)
22194 AvpBSD RET sigaction 0
22194 AvpBSD CALL __getcwd(0x8083000,0x3fc)
22194 AvpBSD RET __getcwd 0
22194 AvpBSD CALL sigaction(0xc,0xbfbff2f8,0)
22194 AvpBSD RET sigaction 0
22194 AvpBSD CALL break(0x8085000)
22194 AvpBSD RET break 0
22194 AvpBSD CALL access(0xbfbff19c,0)
22194 AvpBSD NAMI "/root/.AVP/AvpUnix.ini"
22194 AvpBSD RET access -1 errno 2 No such file or directory
22194 AvpBSD CALL access(0x806ece8,0)
22194 AvpBSD NAMI "AvpUnix.ini"
22194 AvpBSD RET access 0
22194 AvpBSD CALL open(0xbfbff19c,0,0x4)
22194 AvpBSD NAMI "AvpUnix.ini"
22194 AvpBSD RET open 3
22194 AvpBSD CALL lseek(0x3,0,0,0,0x2)
22194 AvpBSD RET lseek 111/0x6f
22194 AvpBSD CALL lseek(0x3,0,0,0,0)
22194 AvpBSD RET lseek 0
22194 AvpBSD CALL break(0x8086000)
22194 AvpBSD RET break 0
22194 AvpBSD CALL read(0x3,0x8085000,0x6f)
22194 AvpBSD GIO fd 3 read 111 bytes
"[AVP32]
DefaultProfile=defUnix.prf
[Configuration]
KeyFile=AvpLinux.key
KeysPath=.
SetFile=avp.set
BasePath=.
"
22194 AvpBSD RET read 111/0x6f
22194 AvpBSD CALL close(0x3)
22194 AvpBSD RET close 0
22194 AvpBSD PSIG SIGSEGV SIG_DFL
22194 AvpBSD NAMI "AvpBSD.core"
All Avp-programs stop the same way.
Leif
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
