Issue 16998 - Crash dump from Redhat 9.0
Summary: Crash dump from Redhat 9.0
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: magrawal
QA Contact: issues@dba
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2003-07-17 05:25 UTC by magrawal
Modified: 2006-05-31 14:29 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Core dump (1.09 MB, application/octet-stream)
2003-07-17 05:27 UTC, magrawal
no flags Details
Crash dump (616.00 KB, application/octet-stream)
2003-07-17 05:29 UTC, magrawal
no flags Details
Core dump (426 bytes, text/plain)
2003-07-25 12:22 UTC, magrawal
no flags Details
Javaldx output (1.42 KB, text/plain)
2003-07-27 03:44 UTC, magrawal
no flags Details
Problem in shares/uno_packages (1.25 KB, text/plain)
2003-07-27 03:45 UTC, magrawal
no flags Details
Javaldx stacktrace (3.20 KB, text/plain)
2003-07-27 04:09 UTC, magrawal
no flags Details
Output from ldd (1.75 KB, text/plain)
2003-08-13 12:58 UTC, magrawal
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description magrawal 2003-07-17 05:25: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.
Comment 1 magrawal 2003-07-17 05:27:55 UTC
Created attachment 7787 [details]
Core dump
Comment 2 magrawal 2003-07-17 05:29:49 UTC
Created attachment 7788 [details]
Crash dump
Comment 3 joergbudi 2003-07-20 08:59:54 UTC
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
Comment 4 eugenetswong 2003-07-21 20:40:20 UTC
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.
Comment 5 joergbudi 2003-07-21 21:04:07 UTC
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. ).
Comment 6 magrawal 2003-07-25 12:22:26 UTC
Created attachment 8021 [details]
Core dump
Comment 7 magrawal 2003-07-25 12:24:38 UTC
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
Comment 8 dankegel 2003-07-26 22:09:57 UTC
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?
Comment 9 joergbudi 2003-07-26 22:42:15 UTC
Or even better, do a 

gdb ./javaldx ./core

where

to get a readable stacktrace.
Comment 10 magrawal 2003-07-27 03:44:45 UTC
Created attachment 8048 [details]
Javaldx output
Comment 11 magrawal 2003-07-27 03:45:28 UTC
Created attachment 8049 [details]
Problem in shares/uno_packages
Comment 12 magrawal 2003-07-27 03:52:37 UTC
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)
Comment 13 magrawal 2003-07-27 04:09:20 UTC
Created attachment 8050 [details]
Javaldx stacktrace
Comment 14 magrawal 2003-07-27 04:11:14 UTC
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.
Comment 15 joergbudi 2003-07-30 21:37:56 UTC
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
Comment 16 magrawal 2003-08-13 12:58:25 UTC
Created attachment 8425 [details]
Output from ldd
Comment 17 joergbudi 2003-08-13 21:10:14 UTC
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

Comment 18 magrawal 2003-08-13 21:54:48 UTC
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
Comment 19 dankegel 2003-09-13 21:09:57 UTC
rc4 is ready... please try it...
Comment 20 utomo99 2003-10-20 12:16:30 UTC
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 
Comment 21 marc.neumann 2003-11-17 09:34:28 UTC
Hi,

is this issue fixed in OOo 1.1. Or does this issue still occure.

Bye Marc
Comment 22 hans_werner67 2004-02-02 13:03:20 UTC
change subcomponent to 'none'
Comment 23 flibby05 2004-03-06 14:53:52 UTC
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
Comment 24 magrawal 2004-03-10 19:51:09 UTC
will do
Comment 25 mandreiana 2004-10-11 16:22:25 UTC
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.
Comment 26 flibby05 2004-10-12 16:47:55 UTC
yes, ready for closing, because reporter did not respond
Comment 27 flibby05 2004-10-12 16:48:15 UTC
closing
Comment 28 magrawal 2004-10-12 17:31:09 UTC
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.