[Open Office] 32-bit OOo crashes - non-implemented umask ?

Petr Mladek pmladek at suse.cz
Tue Sep 19 14:46:04 EDT 2006


Hello,

I am not able to run the current 32-bit build of ood680-m4 with ooo-build 
HEAD. It has happened also with m2, m3. The strange thing is that it works 
with 64-bit build on x86_64.

Here is some output from strace:

--- cut ---
[pid 18789] 
access("/usr/lib/ooo-2.0/share/uno_packages/cache/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/registry/data/org/openoffice/ucb", 
F_OK) = -1 ENOENT (No such file or directory)
[pid 18789] 
access("/home/pmladek/.ooo-2.0/user/uno_packages/cache/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/registry/data/org/openoffice/ucb", 
F_OK) = -1 ENOENT (No such file or directory)
[pid 18789] stat64(0xffd45bd0, 0xffd46bd0) = -1 ENOENT (No such file or 
directory)
[pid 18789] access("/tmp/sv4mm.tmp", F_OK) = 0
[pid 18789] lstat64(0x81d8cc0, 0xffd47308) = 0
[pid 18789] open("/tmp/sv4mm.tmp", O_RDONLY|O_NONBLOCK|O_LARGEFILE|
O_DIRECTORY) = 18
[pid 18789] fstat64(0x12, 0xffd462cc)   = 0
[pid 18789] fcntl64(18, F_SETFD, FD_CLOEXEC) = 0
[pid 18789] getdents64(18, /* 2 entries */, 4096) = 48
[pid 18789] getdents64(18, /* 0 entries */, 4096) = 0
[pid 18789] close(18)                   = 0
[pid 18789] rmdir("/tmp/sv4mm.tmp")     = 0
[pid 18789] mkdir("/tmp", 0777)         = -1 EEXIST (File exists)
[pid 18789] umask(077 <unfinished ...>
[pid 18789] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
[pid 18789] <... umask resumed> )       = -1 ENOSYS (Function not implemented)
[pid 18790] <... futex resumed> )       = -1 EINTR (Interrupted system call)
[pid 18791] <... accept resumed> 0, NULL) = ? ERESTARTSYS (To be restarted)
[pid 18792] <... poll resumed> [{fd=16, events=POLLIN}, {fd=15, 
events=POLLIN}], 2, 4294967295) = -1 EINTR (Interrupted system call)
--- cut ---


Huh, I am mixed by the line:
--- cut ---
[pid 18789] <... umask resumed> )       = -1 ENOSYS (Function not implemented)
--- cut ---

I think that it could be related to the crash. Do you have any idea what went 
wrong?


Thanks in advance.


-- 
Best Regards,

Petr Mladek
software developer
---------------------------------------------------------------------  
SUSE LINUX, s. r. o.                        e-mail: pmladek at suse.cz
Lihovarská 1060/12                          tel: +420 284 028 952
190 00 Prague 9                             fax: +420 284 028 951
Czech Republic                              http://www.suse.cz/


More information about the Openoffice mailing list