|
From: Paul M. <pa...@sa...> - 2004-08-26 12:08:45
|
Are other people able to run OpenOffice successfully under Valgrind at the moment? I tried it on PPC just now and it bombed out, but then I tried it on x86 and it bombed out there also, so I conclude it's not a PPC-specific bug. :) The command line I am using is: LD_LIBRARY_PATH=/usr/lib/openoffice/program valgrind --tool=memcheck \ /usr/lib/openoffice/program/soffice.bin On x86, it prints an error message like this: Bootstrap failing: 'Couldn't open registry file:///home/paulus/valgrind/valgrind-x86/coregrind/types.rdb for reading' followed by several Valgrind errors, then pops up a window saying that the program cannot be started, with a button in it, and when you click the button it exits. It does the same with --tool=corecheck. If I leave out the "valgrind --tool=memcheck" in the command line it starts up just fine. Paul. |
|
From: Tom H. <th...@cy...> - 2004-08-26 12:20:39
|
In message <166...@ca...>
Paul Mackerras <pa...@sa...> wrote:
> The command line I am using is:
>
> LD_LIBRARY_PATH=/usr/lib/openoffice/program valgrind --tool=memcheck \
> /usr/lib/openoffice/program/soffice.bin
>
> On x86, it prints an error message like this:
>
> Bootstrap failing: 'Couldn't open registry file:///home/paulus/valgrind/valgrind-x86/coregrind/types.rdb for reading'
>
> followed by several Valgrind errors, then pops up a window saying that
> the program cannot be started, with a button in it, and when you click
> the button it exits.
Well why is it trying to open such a file? I assume it must be doing
something horrible like trying to scan the mapped objects and then
open a registry file for each one which won't work if valgrind has
injected some extra object files...
For the record the 1.0.2 build on my RedHat 9 box doesn't fail like
that - it just issues a number of warnings and then dies with a SEGV.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Tom H. <th...@cy...> - 2004-08-26 12:28:22
|
In message <yek...@au...>
Tom Hughes <th...@cy...> wrote:
> For the record the 1.0.2 build on my RedHat 9 box doesn't fail like
> that - it just issues a number of warnings and then dies with a SEGV.
If I trace system calls, it does seem to be poking about in
valgrind before it dies:
SYSCALL[5266,1](196):lstat64 ( 0xAFEFB620(/tmp), 0xAFEFB560 )
SYSCALL[5266,1](196):lstat64 ( 0xAFEFB620(/tmp/valgrind-debug), 0xAFEFB560 )
SYSCALL[5266,1](196):lstat64 ( 0xAFEFB620(/tmp/valgrind-debug/bin), 0xAFEFB560 )
SYSCALL[5266,1](196):lstat64 ( 0xAFEFB620(/tmp/valgrind-debug/bin/valgrind), 0xAFEFB560 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64144.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64144.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64101.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64101.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64149.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64149.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64133.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64133.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64139.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64139.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64134.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64134.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64131.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64131.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64146.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64146.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64190.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64190.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64199.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64199.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64155.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64155.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64103.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64103.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64148.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64148.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64147.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64147.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64199.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64199.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64147.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64147.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64135.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64135.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64131.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64131.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64145.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64145.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64137.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64137.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64186.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64186.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64188.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64188.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64181.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64181.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64136.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64136.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64142.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64142.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64107.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64107.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64196.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64196.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64130.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64130.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64182.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64182.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64182.res), 0 )
SYSCALL[5266,1]( 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64182.res), 0 )
==5266==
==5266== Process terminating with default action of signal 11 (SIGSEGV)
==5266== Access not within mapped region at address 0x384
==5266== at 0x3AE86F8A: ResMgr::GetResource(ResId const&, Resource const*) (in /usr/lib/openoffice/program/libtl641li.so)
==5266== by 0x3AE84377: String::String(ResId const&) (in /usr/lib/openoffice/program/libtl641li.so)
==5266== by 0x3AC8816C: Button::GetStandardText(unsigned short) (in /usr/lib/openoffice/program/libvcl641li.so)
==5266== by 0x3AC8B485: OKButton::ImplInit(Window*, unsigned long) (in /usr/lib/openoffice/program/libvcl641li.so)
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Nicholas N. <nj...@ca...> - 2004-08-26 12:30:23
|
On Thu, 26 Aug 2004, Paul Mackerras wrote: > Are other people able to run OpenOffice successfully under Valgrind at > the moment? I tried it on PPC just now and it bombed out, but then I > tried it on x86 and it bombed out there also, so I conclude it's not a > PPC-specific bug. :) OpenOffice 1.0.2 works ok for me (well, Memcheck finds *lots* of errors :) on my RH9 box. N |
|
From: Julian S. <js...@ac...> - 2004-08-31 13:43:53
|
On my SuSE 9.1 box, OOo 1.1.1 dies in exactly the same manner and also appeared to be poking about in V before it died. Bah. J On Thursday 26 August 2004 13:28, Tom Hughes wrote: > In message <yek...@au...> > > Tom Hughes <th...@cy...> wrote: > > For the record the 1.0.2 build on my RedHat 9 box doesn't fail like > > that - it just issues a number of warnings and then dies with a SEGV. > > If I trace system calls, it does seem to be poking about in > valgrind before it dies: > > SYSCALL[5266,1](196):lstat64 ( 0xAFEFB620(/tmp), 0xAFEFB560 ) > SYSCALL[5266,1](196):lstat64 ( 0xAFEFB620(/tmp/valgrind-debug), 0xAFEFB560 > ) SYSCALL[5266,1](196):lstat64 ( 0xAFEFB620(/tmp/valgrind-debug/bin), > 0xAFEFB560 ) SYSCALL[5266,1](196):lstat64 ( > 0xAFEFB620(/tmp/valgrind-debug/bin/valgrind), 0xAFEFB560 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64144.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64144.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64101.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64101.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64149.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64149.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64133.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64133.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64139.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64139.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64134.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64134.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64131.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64131.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64146.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64146.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64190.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64190.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64199.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64199.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64155.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64155.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64103.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64103.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64148.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64148.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64147.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64147.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64199.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64199.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64147.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64147.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64135.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64135.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64131.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64131.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64145.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64145.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64137.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64137.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64186.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64186.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64188.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64188.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64181.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64181.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64136.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64136.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64142.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64142.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64107.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64107.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64196.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64196.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64130.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64130.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64182.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64182.res), 0 ) SYSCALL[5266,1]( > 33):access ( 0xAFEFC420(/tmp/valgrind-debug/bin/resource/vcl64182.res), 0 ) > SYSCALL[5266,1]( 33):access ( > 0xAFEFC420(/tmp/valgrind-debug/bin/vcl64182.res), 0 ) ==5266== > ==5266== Process terminating with default action of signal 11 (SIGSEGV) > ==5266== Access not within mapped region at address 0x384 > ==5266== at 0x3AE86F8A: ResMgr::GetResource(ResId const&, Resource > const*) (in /usr/lib/openoffice/program/libtl641li.so) ==5266== by > 0x3AE84377: String::String(ResId const&) (in > /usr/lib/openoffice/program/libtl641li.so) ==5266== by 0x3AC8816C: > Button::GetStandardText(unsigned short) (in > /usr/lib/openoffice/program/libvcl641li.so) ==5266== by 0x3AC8B485: > OKButton::ImplInit(Window*, unsigned long) (in > /usr/lib/openoffice/program/libvcl641li.so) > > Tom |
|
From: James B. <ja...@ha...> - 2004-08-31 14:15:23
|
Hmmm ... the OOo (1.1.2) and V (2.1.3.CVS from last week) combination seems to work OK on my redhat 9 box. Well, at least I get a whole list of errors from memcheck ;) hafnasandur/home/james/temp [322] valgrind --tool=memcheck -v --trace-children=yes ooffice ../ices/FF.doc [snip lots of output] --8222-- supp: 215 Ugly strchr error in /lib/ld-2.3.2.so --8222-- supp: 9 realpath stupidity part II --8222-- supp: 366 realpath is inefficiently coded ==8222== ==8222== IN SUMMARY: 1454 errors from 64 contexts (suppressed: 590 from 3) ==8222== ==8222== malloc/free: in use at exit: 2728755 bytes in 140672 blocks. ==8222== malloc/free: 166307 allocs, 25635 frees, 7775457 bytes allocated. [snip] interestingly, if I specify a log file then it all goes pear-shaped hafnasandur/home/james/temp [323] valgrind --tool=memcheck -v --log-file=ooffice.log --trace-children=yes ooffice ../ices/FF.doc valgrind: Bad option `--log-file=<file> didn't work out for some reason.'; aborting. valgrind: Use --help for more information. /usr/bin/ooffice: line 84: cd: ==8502== Can't create/open log file `ooffice.log.pid8502'; giving up!: No such file or directory /usr/bin/ooffice: line 232: /usr/bin/pagein: No such file or directory /usr/bin/ooffice: line 239: /usr/bin/soffice.bin: No such file or directory /usr/bin/ooffice: line 239: exec: /usr/bin/soffice.bin: cannot execute: No such file or directory Cheers, James. On Tue, 2004-08-31 at 13:43, Julian Seward wrote: > On my SuSE 9.1 box, OOo 1.1.1 dies in exactly the same manner > and also appeared to be poking about in V before it died. Bah. > > J > > > On Thursday 26 August 2004 13:28, Tom Hughes wrote: > > In message <yek...@au...> > > > > Tom Hughes <th...@cy...> wrote: > > > For the record the 1.0.2 build on my RedHat 9 box doesn't fail like > > > that - it just issues a number of warnings and then dies with a SEGV. > > > > If I trace system calls, it does seem to be poking about in > > valgrind before it dies: > > James Begley -- Telephone: +354-552-0240. Marine Research Institute, Skulagata 4, P.O. Box 1390, 121 Reykjavik, Iceland. |
|
From: Jeremy F. <je...@go...> - 2004-08-31 15:07:08
|
On Thu, 2004-08-26 at 13:20 +0100, Tom Hughes wrote: > Well why is it trying to open such a file? I assume it must be doing > something horrible like trying to scan the mapped objects and then > open a registry file for each one which won't work if valgrind has > injected some extra object files... OO seems to do quite a bit of digging around in /proc; I had already changed the way Valgrind's exec works so that when OO looks at /proc/ self/cmdline, it appears as it would expect. I've been really hoping we can avoid having to implement a general /proc emulator. J |
|
From: Robert W. <rj...@du...> - 2004-08-31 18:12:01
|
> OO seems to do quite a bit of digging around in /proc; I had already > changed the way Valgrind's exec works so that when OO looks at /proc/ > self/cmdline, it appears as it would expect. I've been really hoping we > can avoid having to implement a general /proc emulator. Have you committed this patch? We're running into the same problem with some of our software at work, so it sounds like a useful thing. |
|
From: Jeremy F. <je...@go...> - 2004-08-31 20:55:33
|
On Tue, 2004-08-31 at 11:11 -0700, Robert Walsh wrote: > > OO seems to do quite a bit of digging around in /proc; I had already > > changed the way Valgrind's exec works so that when OO looks at /proc/ > > self/cmdline, it appears as it would expect. I've been really hoping we > > can avoid having to implement a general /proc emulator. > > Have you committed this patch? We're running into the same problem with > some of our software at work, so it sounds like a useful thing. Yep, the cmdline stuff has been in there for ages - it's all that stuff which passes the Valgrind commandline args in the environment rather than as args. I haven't really thought about general /proc simulator, because that's hard (or at least fiddly). J |