Bug 54594 - KPovModeler crash in startup
Summary: KPovModeler crash in startup
Status: RESOLVED INTENTIONAL
Alias: None
Product: kpovmodeler
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: KPovModeler mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-13 12:13 UTC by iakynet
Modified: 2005-07-17 10:45 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Build error (203.10 KB, text/plain)
2005-01-13 18:50 UTC, Anderson Medeiros Gomes
Details

Note You need to log in before you can comment on or make changes to this bug.
Description iakynet 2003-02-13 12:13:35 UTC
Version:           desconocido (using KDE 3.1.0)
Installed from:    compiled sources
Compiler:          gcc version 3.2.1
OS:          Linux (i686) release 2.4.19

When i start KPovModeler for the first time it crash. It never start fine: crash all times i try to start it. This is the backtrace:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1024 (LWP 30962)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x415a5609 in wait4 () from /lib/libc.so.6
#0  0x415a5609 in wait4 () from /lib/libc.so.6
#1  0x4161add0 in __check_rhosts_file () from /lib/libc.so.6
#2  0x413f5eeb in waitpid () from /lib/libpthread.so.0
#3  0x40b466ec in KCrash::defaultCrashHandler(int) ()
   from /usr/local/kde/lib/libkdecore.so.4
#4  0x413f3a44 in pthread_sighandler () from /lib/libpthread.so.0
#5  0x4152e518 in sigaction () from /lib/libc.so.6
#6  0x4087a445 in KAction::initPrivate(QString const&, KShortcut const&, QObject const*, char const*) () from /usr/local/kde/lib/libkdeui.so.4
#7  0x408785df in KAction::KAction(QString const&, KShortcut const&, QObject const*, char const*, KActionCollection*, char const*) ()
   from /usr/local/kde/lib/libkdeui.so.4
#8  0x400cd981 in PMPart::initActions() ()
   from /usr/local/kde/lib/kde3/libkpovmodelerpart.so
#9  0x400cd00e in PMPart::PMPart(QWidget*, char const*, QObject*, char const*, bool, PMShell*) () from /usr/local/kde/lib/kde3/libkpovmodelerpart.so
#10 0x400e023e in PMShell::PMShell(KURL const&) ()
   from /usr/local/kde/lib/kde3/libkpovmodelerpart.so
#11 0x08048c21 in main ()
#12 0x4151e0bf in __libc_start_main () from /lib/libc.so.6

Regards,
Ignacio.
Comment 1 Andreas Zehender 2003-02-13 19:43:27 UTC
Subject: Re:  New: KPovModeler crash in startup

Hi!

Please recompile KPovModeler with debug information
(./configure --enable-debug) and resent me the backtrace.

Andreas


On Thursday 13 February 2003 12:13, you wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=54594
>            Summary: KPovModeler crash in startup
>            Product: kpovmodeler
>            Version: unspecified
>           Platform: Compiled Sources
>         OS/Version: Linux
>             Status: UNCONFIRMED
>           Severity: crash
>           Priority: NOR
>          Component: general
>         AssignedTo: zehender@kde.org
>         ReportedBy: iakynet@eresmas.com
>
>
> Version:           desconocido (using KDE 3.1.0)
> Installed from:    compiled sources
> Compiler:          gcc version 3.2.1
> OS:          Linux (i686) release 2.4.19
>
> When i start KPovModeler for the first time it crash. It never start fine:
> crash all times i try to start it. This is the backtrace:
>
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...[New Thread 1024 (LWP 30962)]
> (no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> 0x415a5609 in wait4 () from /lib/libc.so.6
> #0  0x415a5609 in wait4 () from /lib/libc.so.6
> #1  0x4161add0 in __check_rhosts_file () from /lib/libc.so.6
> #2  0x413f5eeb in waitpid () from /lib/libpthread.so.0
> #3  0x40b466ec in KCrash::defaultCrashHandler(int) ()
>    from /usr/local/kde/lib/libkdecore.so.4
> #4  0x413f3a44 in pthread_sighandler () from /lib/libpthread.so.0
> #5  0x4152e518 in sigaction () from /lib/libc.so.6
> #6  0x4087a445 in KAction::initPrivate(QString const&, KShortcut const&,
> QObject const*, char const*) () from /usr/local/kde/lib/libkdeui.so.4 #7 
> 0x408785df in KAction::KAction(QString const&, KShortcut const&, QObject
> const*, char const*, KActionCollection*, char const*) () from
> /usr/local/kde/lib/libkdeui.so.4
> #8  0x400cd981 in PMPart::initActions() ()
>    from /usr/local/kde/lib/kde3/libkpovmodelerpart.so
> #9  0x400cd00e in PMPart::PMPart(QWidget*, char const*, QObject*, char
> const*, bool, PMShell*) () from
> /usr/local/kde/lib/kde3/libkpovmodelerpart.so #10 0x400e023e in
> PMShell::PMShell(KURL const&) ()
>    from /usr/local/kde/lib/kde3/libkpovmodelerpart.so
> #11 0x08048c21 in main ()
> #12 0x4151e0bf in __libc_start_main () from /lib/libc.so.6
>
> Regards,
> Ignacio.

Comment 2 Andreas Zehender 2003-02-14 17:25:30 UTC
Subject: Re:  KPovModeler crash in startup

Hi!

On Friday 14 February 2003 10:48, you wrote:
> OK, this is the new backtrace:
>
> [New Thread 1024 (LWP 12624)]
> 0x415a5609 in wait4 () from /lib/libc.so.6
> #0  0x415a5609 in wait4 () from /lib/libc.so.6
> #1  0x4161add0 in __check_rhosts_file () from /lib/libc.so.6
> #2  0x413f5eeb in waitpid () from /lib/libpthread.so.0
> #3  0x40b466ec in KCrash::defaultCrashHandler(int) ()
>    from /usr/local/kde/lib/libkdecore.so.4
> #4  0x413f3a44 in pthread_sighandler () from /lib/libpthread.so.0
> #5  0x4152e518 in sigaction () from /lib/libc.so.6
> #6  0x4087a445 in KAction::initPrivate(QString const&, KShortcut const&,
> QObject const*, char const*) () from /usr/local/kde/lib/libkdeui.so.4
> #7  0x408785df in KAction::KAction(QString const&, KShortcut const&,
> QObject const*, char const*, KActionCollection*, char const*) ()
>    from /usr/local/kde/lib/libkdeui.so.4
> #8  0x400cd9a1 in PMPart::initActions() (this=0x80dcb18) at pmpart.cpp:152
> #9  0x400cd02e in PMPart (this=0x80dcb18, parentWidget=0xfffffe00,
>     widgetName=0xfffffe00 <Address 0xfffffe00 out of bounds>,
>     parent=0xfffffe00, name=0xfffffe00 <Address 0xfffffe00 out of bounds>,
>     readwrite=true, shell=0xfffffe00) at pmpart.cpp:121
> #10 0x400e026e in PMShell (this=0x80cf060, url=@0xbffff374) at
> pmshell.cpp:51 #11 0x08048c21 in main (argc=-512, argv=0xfffffe00) at
> main.cpp:61

The KPovModeler call in pmpart.cpp (#8) is correct and not the reason of the 
crash.
Either your kdelibs is buggy (do you use a CVS version, a release candidate or 
a stable release?) or there are some binary incompatibilities between the 
library KPovModeler was linked against and the library it uses at runtime. 
Are you sure these two libraries are the same?

If you have enough disk space and time, you could recompile kdelibs with debug 
information, too and send me the backtrace again.

> Oh!, and i buid kdegraphics with the flags "-march=i686 -O3 -pipe". If you
> like, i can recompile without this.

That shouldn't make a difference (in theory).

Andreas

Comment 3 Andreas Zehender 2003-04-09 07:32:39 UTC
Hi! 
 
This seems to be a kde or compiler issue, but not a kpovmodeler bug. I found similar 
crashes for other kde programs. The maintainers all said that this problem went away 
with newer kde versions or different compilers. 
Comment 4 iakynet 2003-04-09 22:35:55 UTC
Subject: Re:  KPovModeler crash in startup

> Hi!

Hi Andreas,

> This seems to be a kde or compiler issue, but not a kpovmodeler bug. I
> found similar crashes for other kde programs. The maintainers all said that
> this problem went away with newer kde versions or different compilers.

Yes, i think the same...

Oh!, and i forget to said you that kpovmodeler works fine in FreeBSD 4.7, 
compiled from ports... so the problem must be in my Linux and/or compiler 
configuration and/or version: it crash again in KDE 3.1.1 on Linux... :-(

Regards,
Ignacio.
Comment 5 Anderson Medeiros Gomes 2004-12-16 05:32:21 UTC
What about my backtrace?

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -150555776 (LWP 2956)]
[KCrash handler]
#4  0xe85b2607 in ?? ()
#5  0x085a33e5 in ?? ()
#6  0x03d81f04 in __dynamic_cast () from /usr/lib/libGLU.so.1
#7  0x00db6454 in KAction::initPrivate (this=0x85e3f28, text=@0xfee84520, 
    cut=@0xfee844c0, receiver=0x85a2ce0, slot=0x92a0ed "1slotFileImport( )")
    at qobject.h:154
#8  0x00db766f in KAction (this=0x85e3f28, text=@0xfee84520, cut=@0xfee844c0, 
    receiver=0x85a2ce0, slot=0x92a0ed "1slotFileImport( )", parent=0x85a33e0, 
    name=0x92a0e1 "file_import") at kaction.cpp:117
#9  0x0072f99b in PMPart::initActions (this=0x85a2ce0) at pmpart.cpp:244
#10 0x0072e841 in PMPart (this=0x85a2ce0, parentWidget=0x859ac20, 
    widgetName=0x92cc19 "part", parent=0x859ac20, name=0x92cc19 "part", 
    readwrite=true, shell=0x85a33e0) at pmpart.cpp:142
#11 0x00741051 in PMShell (this=0x859ac20, url=@0xfee84640) at pmshell.cpp:55
#12 0x08049017 in main (argc=1, argv=0xfee847e4) at main.cpp:64
Comment 6 Thiago Macieira 2004-12-16 11:07:20 UTC
It crashed inside dynamic_cast, inside libGLU.so. That doesn't look like a KDE problem.

Wild guess: you're using NVidia's proprietary drivers and libGLU. Make sure they've been compiled with the same g++ version as your KDE.
Comment 7 Anderson Medeiros Gomes 2005-01-13 18:48:40 UTC
I am using NVidia's proprietary drivers... 1.0-6629. I compiled it using GCC 3.3.3-7 (RedHat). I couldn't build KDE 3.3.2 using the same GCC. When I did, I got a lot of errors. So, I user GCC 3.4.0-1 (RedHat). I like installing software from sources, but when things get wrong, I don't know what to do...

Well, I tried build KDE again, but I couldn't do it again. I am not a Linux developer. Please, I need your help. I don't know what is wrong in my system. See the attachment below. That is my 'make' output when I try building arts-1.3.2.
Comment 8 Anderson Medeiros Gomes 2005-01-13 18:50:34 UTC
Created attachment 9076 [details]
Build error

The 'make' output I have got when I try to build arts-1.3.2.
Comment 9 Anderson Medeiros Gomes 2005-01-23 15:55:41 UTC
Ok... I resolved my kpovmodeler problem. Now, it's working... :-)

My GCC 3.3.3 isn't working well. So, I:
# Built my 2.6.10 kernel using GCC 3.4.0
# Built my Xorg 6.8.1 using GCC 3.4.0
# Built nVidia drivers using GCC 3.4.0
# Rebuilt entire KDE 3.3.2 using GCC 3.4.0

After I did that hard work, I tried to use kpovmodeler again and... CRASH!

But yesterday I deactivated the 'RenderAccel' option in my Xorg.conf. Today, I tried to open kpovmodeler again and... WORKING NOW!
Comment 10 Amaury De Ganseman 2005-07-17 10:45:37 UTC
It crashes if it can't access to /dev/nvidiactl in my case.  Why does it crash because it can't access to this device ?