OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: daniel3000 on July 04, 2007, 06:18:05 am
-
Hi huys, esp. Meanie,
some day ago, I downloaded the "latest" zgcc image by Meanie and compiled GTK apps for beta3.
However, these apps crashed often when calling gnome_vfs_shutdown() or various GTK dialog functions.
Recompiling with an older zgcc by Meanie created intact binaries.
Any ideas why that is?
Can't I use newer zgcc images anymore for beta3?
Thanks
daniel
-
Hi huys, esp. Meanie,
some day ago, I downloaded the "latest" zgcc image by Meanie and compiled GTK apps for beta3.
However, these apps crashed often when calling gnome_vfs_shutdown() or various GTK dialog functions.
Recompiling with an older zgcc by Meanie created intact binaries.
Any ideas why that is?
Can't I use newer zgcc images anymore for beta3?
Thanks
daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164281\"][{POST_SNAPBACK}][/a][/div]
I played with gtkwidget.h and forgot to take out those debugging changes which also broke my pidgin build. anyway, will be fixed when I next upload the zggc image...
-
Hi Meanie,
please let us know when you upload the new one.
But what about that gnome_vfs_shutdown() problem?
Is is also related to gtk_widget.h?
When the applicatin called that function, it crashed.
When compiling with the older zgcc it don't.
Thanks!
daniel
-
Hi Meanie,
please let us know when you upload the new one.
But what about that gnome_vfs_shutdown() problem?
Is is also related to gtk_widget.h?
When the applicatin called that function, it crashed.
When compiling with the older zgcc it don't.
Thanks!
daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164351\"][{POST_SNAPBACK}][/a][/div]
latest zgcc has been uploaded. let me know if you have any problems with this build. the gnome headers have not changed in any zgcc build, the only hacking was done in the gtk/gdk stuff so hopefully this should fix it.
-
latest zgcc has been uploaded. let me know if you have any problems with this build. the gnome headers have not changed in any zgcc build, the only hacking was done in the gtk/gdk stuff so hopefully this should fix it.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164447\"][{POST_SNAPBACK}][/a][/div]
Hi Meanie - what's the url for downloading zgcc?
-
latest zgcc has been uploaded. let me know if you have any problems with this build. the gnome headers have not changed in any zgcc build, the only hacking was done in the gtk/gdk stuff so hopefully this should fix it.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=164447\")
Hi Meanie - what's the url for downloading zgcc?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164453\"][{POST_SNAPBACK}][/a][/div]
It's under [a href=\"http://www.tyrannozaurus.com/feed/pdaXii13/build/zgcc-3.4.6.squashfs]http://www.tyrannozaurus.com/feed/pdaXii13...-3.4.6.squashfs[/url].
Meanie, this image indeed fixes the GTK problems, but the gnome_vfs_shutdown problem is still there.
If I compile notecase with your older zgcc image, it works nicely.
If I compile it with the latest one downloded just an hour ago, notecase crashes at the end when quitting. Using some debug printfs in the sources shows that it is indeed the call of function gnome_vfs_shutdown at the end of main.cpp which causes the crash (segmentation fault).
Could you please have a look at it and - if possible - fix the problem?
I guess you will be able to reproduce it.
Notecase latest sources are available under http://notecase.sourceforge.net/temp (http://notecase.sourceforge.net/temp)
The crash is not directly visible (no output on console), but via the function "signal_handler" in main.cpp on segfault a crashlog file is created in /home/root/.notecase and any debug printf after gnome_vfs_shutdown isn't executed anymore.
Thanks so much!
Why is the latest ygcc image so much larger than the previous ones (over 40MB vs. 28 MB)?
daniel
-
Okay, I tracked down the problem.
It is not due to zgcc, but due to kkazakov's glib2 package.
If I replace the beta3 original glib2 package with kkazakov's glib2 package, I start to get these crashes on gnome_vfs_shutdown.
Probably I'll have to replace some more libs, but replacing gnome-vfs resulted in an even greater mess.
kkazakov, do you know an easy solution to that problem?
I'm now trying to compile glib 2.12.10 myself. Maybe this will help. We'll see when the compilation is finished (next week? ;-) )
daniel
-
That's weird ... i use the custom compiled glib2 all the time without single program to complain. Maybe some other dependencies ? No idea ... anyway - i'm trying to stay as much as possible on the edge ... everything newer that do compiles, i use it.
P.P. Are you sure you used http://z.drun.net/packages/glib2-devel_2.12.4_armv5tel.ipk (http://z.drun.net/packages/glib2-devel_2.12.4_armv5tel.ipk) in order to compile ? or used the old header files ?
-
That's weird ... i use the custom compiled glib2 all the time without single program to complain. Maybe some other dependencies ? No idea ... anyway - i'm trying to stay as much as possible on the edge ... everything newer that do compiles, i use it.
P.P. Are you sure you used http://z.drun.net/packages/glib2-devel_2.12.4_armv5tel.ipk (http://z.drun.net/packages/glib2-devel_2.12.4_armv5tel.ipk) in order to compile ? or used the old header files ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164597\"][{POST_SNAPBACK}][/a][/div]
hi kkazakov,
I compiled my own glib2 package (2.12.9) yesterday, but still the same problems.
Maybe really some other core package. But glib2 was the only one I have updated from beta3 so far. Maybe that's the problem. maybe I have to update more packages.
Re. the header files... well, Meanie's zgcc image contains glib header files (probably the old ones) and I installed your devel package, too.
So how can I make sure that the correct ones are used?
Thanks
daniel
-
Be sure that my include path /usr/include is before Meanie's /opt/native/... whatever is. This maybe is somewhere in the startup script, i'm not sure. Here I have it setup perfectly since some time and not touching it right now
-
Good idea, kkazakov... but I have not found a way to set the include paths yet. Have never fiddled around with them, so I have no idea where to search for them.
In /etc/profile there is nothing about it.
Also, in the Makefile of Notecase there is no include path to set...
Can anyone give a hint please?
Thank you!
daniel
-
Well, I just compiled notecase 1.5.8 with my compilation env. No problems, no crashes, no segfaults, nothing (tried in console) - it just works™.
Turns out that my gilb-devel is simply installed in /usr/include/ and nothing more ... well, i have almost all of my -devel packages installed.
Also, if you want, I can archive my setup and you can extract it somewhere and symlink to /opt/cross ... and then try to use it. I've compiled great number of apps with it
-
Hi kkazakov,
that would be great, if you could package it up.
Re. notecase:
the crash is not obious.
It is just when quitting notecase (where the gnome_vfs_shutdown() function is called), and not visible on the console.
The only sign of it is that notecase generates a crash log file in ~/.notecase
Another sign is that "echo $?" directly after notecase execution returns 1, not 0.
Please recheck that on your setup, so we can be sure that you really have no crash.
Thank you!
daniel
-
Just checked, there is no log in the ~/.notecase/ , only some .ini file. Also, echo returns 0
I think there's no crash
Anyway, i'm about packing it and will post a link for DL, and my /etc/profile changes, what i added for the dev. env.
-
Just checked, there is no log in the ~/.notecase/ , only some .ini file. Also, echo returns 0
I think there's no crash
Anyway, i'm about packing it and will post a link for DL, and my /etc/profile changes, what i added for the dev. env.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164769\"][{POST_SNAPBACK}][/a][/div]
This is funny.
Using your notecase 1.5.8 package you just announced on the announcement
thread, I again get the crash.
Probably, if I give you my self-compiled notecase which causes the crash here, you won't get the crash either.
The funny thing is:
The only relevant part which I have changed from a system which did not produce that crash to the current state is that I installed your glib2 and glib2-devel package.
What does that tell us?
Do you have a clue how I can debug this problem?
Thanks!
daniel
-
Well, no idea.
here's mine - http://z.drun.net/gcc-3.4.6-mine.tar.bz2 (http://z.drun.net/gcc-3.4.6-mine.tar.bz2)
just unpack somewhere where you have storage, and symlink it to /opt/native/.
that's example for my setup:
ln -s /storage/devel/gcc-3.4.6 /opt/native/arm/3.4.6-xscale-softvfp
those are mine changes to /etc/profile (they apply after you relogin) :
###### devel env
export QMAKESPEC=/usr/lib/qt/mkspecs/default/
export QTDIR=/usr/lib/qt
export KDEDIR=/usr/lib/kde
export KDEDIRS=$KDEDIR
export LD_LIBRARY_PATH=$KDEDIR/lib:/opt/native/arm/3.4.6-xscale-softvfp/lib:$QTDIR/lib:/opt/native/arm/3.4.6-xscale-softvfp/armv5tel-cacko-linux/qt3/lib:$KDEDIR/lib:/usr/lib:$LD_LIBRARY_PATH
export NATIVE_SDK_FILES_PREFIX=/opt/native/arm/3.4.6-xscale-softvfp/armv5tel-cacko-linux
export QMAKESPEC=/opt/native/arm/3.4.6-xscale-softvfp/armv5tel-cacko-linux/qt3/mkspecs/default
export DISTCC_HOSTS="192.168.129.1 localhost"
export PKG_CONFIG_PATH=/usr/lib/pkgconfig:/usr/local/lib/pkgconfig:/usr/X11R6/lib/pkgconfig:/opt/native/arm/3.4.6-xscale-softvfp/armv5tel-cacko-linux/lib/pkgconfig:/opt/native/arm/3.4.5-xscale-softvfp/armv5tel-cacko-linux/lib/pkgconfig:/usr/local/lib/pkgconfig:/usr/X11R6/lib/pkgconfig
export PKG_CONFIG=/opt/native/arm/3.4.6-xscale-softvfp/bin/pkg-config
PATH=$PATH:/opt/native/arm/3.4.6-xscale-softvfp/bin:$QTDIR/bin:$KDEDIR/bin