Apache OpenOffice (AOO) Bugzilla – Issue 16998
Crash dump from Redhat 9.0
Last modified: 2006-05-31 14:29:06 UTC
I am trying to run the SDBC driver in Redhat Linux 9.0 but I am getting a segmentation fault error. I followed the instructions in your offline email and I think I have been able to locate the crash dumps. Please don't get annoyed if these are not the correct dumps, the only clue I have is that they were created at the right time and were located in the OO/program directory. Surprisingly, there were 2 core dumps, I am attaching both. I was able to run ./pkgchk -net successfully on my W2K desktop.
Created attachment 7787 [details] Core dump
Created attachment 7788 [details] Crash dump
Hi, please identify the correct core (e.g. by looking at the timestamp ). Please don't attach the complete cores. do a gdb ./pkgchk.bin core.xxxx (where xxxx is the number). and type where, which should give you a callstack, that you should attach here. Bye, Joerg
Hi. I'm adding the oooqa keyword & my email address to the cc field. Joerg, would you be willing to add the oooqa keyword when you've commented on an issue? I ask this because it helps us to know which issues are fresh & haven't been commented on by any members of OOo. It's isn't a big deal, but it would save a few minutes, & help to make our statistics more accurate.
Actually, I forgot to reset the owner to magrawal. Please provide a readable stacktrace as I mentioned in an earlier comment. to Eugene: Do you have a link, where this is explained (e.g. when to remove the keyword again, what the meaning of this keyword is, etc. ).
Created attachment 8021 [details] Core dump
I have attached the stacktrace. But I am not sure if what I have submitted is useful. If it is useful to get the actual method/ class names and you can tell me what I should do to get them in the trace, let me know and I will try to get them
o-ho! The crash is in javaldx! magrawal, can you try the command /opt/OpenOffice.org1.1Beta/program/javaldx at a shell prompt, and tell us what it says?
Or even better, do a gdb ./javaldx ./core where to get a readable stacktrace.
Created attachment 8048 [details] Javaldx output
Created attachment 8049 [details] Problem in shares/uno_packages
I have attached the output while running ./javaldx. It is in the file javaldx. The file shows that there is no problem in ./pkgchk with OO1. 1RC but in OO1.1Beta, some file appeared to be missing. I still have 2 problems: 1. The simple one: It also turned out that I got errors while trying . /pkgchk --shared in OO1.1RC. I deleted the .zip file from user/uno_packages and ran ./pkgchk before doing ./pkgchk --shared. The output is in pkgchk_shared 2. The difficult one: After successfully running ./pkgchk, when I tried creating a new data source, I did not find the postgresql option in the datasources list. I am logged in as root in Redhat 9.0 (I login as root because most of the captions are missing in dialogs when I login as a user)
Created attachment 8050 [details] Javaldx stacktrace
I finally managed to get the stacktrace which is attached as file stacktrace. The bad news is that the problems were in OO1.1Beta2, pkgchk ran fine in OO1.1RC on Redhat 9.0 Unfortunately, I will need help in getting postgresql in the datasources drop-down list though ./pkgchk ran fine.
Hi, please unzip the uno-package to a temporary directory. Then switch to the OOo/program directory. do a $ tcsh $ setenv LD_LIBRARY_PATH . $ ldd -r /path/to/tmp-dir/linux_x86.plt/* and add the output to this issue. Bye, Joerg Bye, Joerg
Created attachment 8425 [details] Output from ldd
Hi, this is the problem libstdc++.so.3 => not found I just got to know some days ago, that rc2 was built with a compiler, which may produce code, that is incompatible to older releases. So the driver needs to be rebuilt on the linux platform with the new official compiler (I think, gcc-3.3.x). As I am behind a low bandwidth internet connection, I skipped the rc2 buildenvironment. So I currently don't have a environment at home to do the build. I currently wait for rc3, which is supposed to appear in about one and a half week. I will then provide a new build. Alternatively, you may try to find someone, who rebuilds the lib with the build instructions given on the driver's homepage. Sorry to have such bad news. Bye, Joerg
Thanks, If building is easy, I don't mind trying to do the build, I am kind of apprehensive to try these adventures. I just want to be able to tell people how to get a good database solution with OO. Look forward to your build with RC3. It would be awesome if the OO database access system could be used to create tables, queries, views and administer the database itself. Do you think it is going to happen? What will it take to do it? Manish
rc4 is ready... please try it...
Please try using the latest OpenOffice 1.1 Final , you can download it from www.openoffice.org many bug fixes and enhancements since your version and 1.1 Final . If the problem still happend in 1.1 please report back
Hi, is this issue fixed in OOo 1.1. Or does this issue still occure. Bye Marc
change subcomponent to 'none'
hi magrawal, OpenOffice 1.1.1 will be released during the next few days. Could you please retry if the problem still exists with this build? Please let us know about the result by posting a short comment to this issue. max
will do
As we got now answer, ok to close? Found only one report with RH9 problems, but related to something else. Anyway, RH9 is quite old.
yes, ready for closing, because reporter did not respond
closing
Thanks for closing. I am sorry for not replying but I had meant to rig up a RH9 system to test OO1.1.3 on RH9. I have since upgraded/ changed to JDS and do not have access to RH9 so I have not been successful. I agree with closing as suggested.