Skip to contentSkip to conversation

Segmentation fault with "hob"-command (now no html)

DISCUSSION [email protected] 3 participants 3 messages Feb 14, 2012 – Feb 15, 2012

lore
Share & tools
lore
#0 lore raw

Sorry for the last post in HTML-Format.
I didn't recognize that my provider has changed the format and doesn't send text-messages any more.
Perhaps the admin may delete my wrong post.

Hello,
I am evaluating Yocto, therefore sorry, if it is a beginner fault; I have a problem starting "hob".
After the command "hob" the system tells that some tools have to be built. The build ends
with the following lines:

------------- snip ---------------------------------------
...
NOTE: package pseudo-native-1.1.1-r2: task do_populate_sysroot: Started
NOTE: package pseudo-native-1.1.1-r2: task do_populate_sysroot: Succeeded
NOTE: Tasks Summary: Attempted 126 tasks of which 0 didn't need to be rerun and 0 failed.
/Yocto/poky-edison-6.0/scripts/bitbake: Zeile 86: 14880
Speicherzugriffsfehler PSEUDO_BINDIR=$PSEUDOBINDIR
PSEUDO_LIBDIR=$PSEUDOBINDIR/../lib/pseudo/lib PSEUDO_PREFIX=$PSEUDOBINDIR/../../ PSEUDO_DISABLED=1 $PSEUDOBINDIR/pseudo $BITBAKE $@

------------- snap --------------------------------------- German output: "Speicherzugriffsfehler" = "segmentation fault"

System-infos:
Build-System: OpenSuSE 11.3, 32bit
Yocto version: "poky-edison-6.0-tar-bz2" from the Yokto download server

The absolute same problem also appears with the following constellation:
Build system: OpenSuSE 11.3 64bit
Yocto version: "poky-edison-6.0-tar-bz2 'from yocto download server

On the 64-bit system, I have the "nightly build" ("http://autobuilder.yoctoproject.org/nightly/20120213-1/yocto.tar.bz2") reinstalled.
Here I get the following output:
------------- snip ---------------------------------------
...
NOTE: package tar-replacement-native-1.26-r0: task do_populate_sysroot:
Started
NOTE: package tar-replacement-native-1.26-r0: task do_populate_sysroot:
Succeeded
NOTE: Tasks Summary: Attempted 126 tasks of which 0 didn't need to be rerun and 0 failed.
/Yocto/yocto/scripts/bitbake: Zeile 95: 29888 Speicherzugriffsfehler PSEUDO_BINDIR=$PSEUDOBINDIR PSEUDO_LIBDIR=$PSEUDOBINDIR/../lib/pseudo/lib PSEUDO_PREFIX=$PSEUDOBINDIR/../../ PSEUDO_DISABLED=1 $PSEUDOBINDIR/pseudo $BITBAKE $@

------------- snap ---------------------------------------

From a gdb session (evaluation of the core dump) of the nightly build I get the following output:
------------- snip ---------------------------------------
...
Core was generated by `python /Yocto/yocto/bitbake/bin/bitbake -r conf/hob-pre.conf -R conf/hob-post.c'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f0254626c9e in gdk_window_enable_synchronized_configure ()
from /usr/lib64/libgdk-x11-2.0.so.0
(gdb)
------------- snap ---------------------------------------

The error occurred in each case at the first attempt after a new installation.
Commands:
------------- snip --------------------------------------- source oe-init-build-env
hob
------------- snap ---------------------------------------

Changes in "local.conf":

------------- snip --------------------------------------- MACHINE ?= "atom-pc"
------------- snap ---------------------------------------

Is it a bug, or a beginner's mistake?

Thanks in advance,

Siegfried

#1 lore raw

[email protected] wrote on 2012-02-15:

Quoted 64 lines

Sorry for the last post in HTML-Format.
I didn't recognize that my provider has changed the format and doesn't send text-messages any more.
Perhaps the admin may delete my wrong post.

Hello, I am evaluating Yocto, therefore sorry, if it is a beginner fault; I have a problem starting "hob". After the command "hob" the system tells that some tools have to be built. The build ends with the following lines:

------------- snip --------------------------------------- ... NOTE:
package pseudo-native-1.1.1-r2: task do_populate_sysroot: Started NOTE:
package pseudo-native-1.1.1-r2: task do_populate_sysroot: Succeeded
NOTE: Tasks Summary: Attempted 126 tasks of which 0 didn't need to be rerun and 0 failed. /Yocto/poky-edison-6.0/scripts/bitbake: Zeile 86:
14880 Speicherzugriffsfehler PSEUDO_BINDIR=$PSEUDOBINDIR
PSEUDO_LIBDIR=$PSEUDOBINDIR/../lib/pseudo/lib PSEUDO_PREFIX=$PSEUDOBINDIR/../../ PSEUDO_DISABLED=1 $PSEUDOBINDIR/pseudo $BITBAKE $@

------------- snap --------------------------------------- German output: "Speicherzugriffsfehler" = "segmentation fault"

System-infos: Build-System: OpenSuSE 11.3, 32bit Yocto version:
"poky-edison-6.0-tar-bz2" from the Yokto download server

The absolute same problem also appears with the following constellation:
Build system: OpenSuSE 11.3 64bit
Yocto version: "poky-edison-6.0-tar-bz2 'from yocto download server

On the 64-bit system, I have the "nightly build" ("http://autobuilder.yoctoproject.org/nightly/20120213-1/yocto.tar.bz2 ") reinstalled. Here I get the following output: ------------- snip --------------------------------------- ... NOTE: package tar-replacement-native-1.26-r0: task do_populate_sysroot: Started NOTE:
package tar-replacement-native-1.26-r0: task do_populate_sysroot:
Succeeded NOTE: Tasks Summary: Attempted 126 tasks of which 0 didn't need to be rerun and 0 failed. /Yocto/yocto/scripts/bitbake: Zeile 95:
29888 Speicherzugriffsfehler PSEUDO_BINDIR=$PSEUDOBINDIR PSEUDO_LIBDIR=$PSEUDOBINDIR/../lib/pseudo/lib PSEUDO_PREFIX=$PSEUDOBINDIR/../../ PSEUDO_DISABLED=1 $PSEUDOBINDIR/pseudo $BITBAKE $@

------------- snap ---------------------------------------

From a gdb session (evaluation of the core dump) of the nightly build I get the following output:
------------- snip ---------------------------------------
...
Core was generated by `python /Yocto/yocto/bitbake/bin/bitbake -r conf/hob-pre.conf -R conf/hob-post.c'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f0254626c9e in gdk_window_enable_synchronized_configure ()
from /usr/lib64/libgdk-x11-2.0.so.0
(gdb)
------------- snap ---------------------------------------

The error occurred in each case at the first attempt after a new installation. Commands: ------------- snip --------------------------------------- source oe-init-build-env hob ------------- snap ---------------------------------------

Quoted 7 lines

Changes in "local.conf":

------------- snip --------------------------------------- MACHINE ?= "atom-pc"
------------- snap ---------------------------------------

Is it a bug, or a beginner's mistake?

This seems a pygtk bug of bitbake that only appears on some Linux distribution? In my Ubuntu 11.04, I don't get the SegFault.

Thanks,
-- Dexuan

#2 lore raw

Hello Dexuan,

thank you fort hat hint.
The problem was that I was working as "root" and did a "su - <user>". Doing that the environment seems to be different to a normal login. I've played around with the "DISPLAY" environment variable and "xhost". Now it works. Trying to start "hob" as normal user works without any intervention.

Thanks again,

Siegfried

Quoted 85 lines

-----Ursprüngliche Nachricht-----
Von: Cui, Dexuan [mailto:[email protected]]
Gesendet: Mittwoch, 15. Februar 2012 03:42
An: [email protected]; [email protected]
Cc: Joshua Lock
Betreff: RE: [yocto] Segmentation fault with "hob"-command (now no html)

[email protected] wrote on 2012-02-15:

Quoted 64 lines

Sorry for the last post in HTML-Format.
I didn't recognize that my provider has changed the format and doesn't send text-messages any more.
Perhaps the admin may delete my wrong post.

Hello, I am evaluating Yocto, therefore sorry, if it is a beginner fault; I have a problem starting "hob". After the command "hob" the system tells that some tools have to be built. The build ends with the following lines:

------------- snip --------------------------------------- ... NOTE:
package pseudo-native-1.1.1-r2: task do_populate_sysroot: Started NOTE:
package pseudo-native-1.1.1-r2: task do_populate_sysroot: Succeeded
NOTE: Tasks Summary: Attempted 126 tasks of which 0 didn't need to be rerun and 0 failed. /Yocto/poky-edison-6.0/scripts/bitbake: Zeile 86:
14880 Speicherzugriffsfehler PSEUDO_BINDIR=$PSEUDOBINDIR
PSEUDO_LIBDIR=$PSEUDOBINDIR/../lib/pseudo/lib PSEUDO_PREFIX=$PSEUDOBINDIR/../../ PSEUDO_DISABLED=1 $PSEUDOBINDIR/pseudo $BITBAKE $@

------------- snap --------------------------------------- German output: "Speicherzugriffsfehler" = "segmentation fault"

System-infos: Build-System: OpenSuSE 11.3, 32bit Yocto version:
"poky-edison-6.0-tar-bz2" from the Yokto download server

The absolute same problem also appears with the following constellation:
Build system: OpenSuSE 11.3 64bit
Yocto version: "poky-edison-6.0-tar-bz2 'from yocto download server

On the 64-bit system, I have the "nightly build" ("http://autobuilder.yoctoproject.org/nightly/20120213-1/yocto.tar.bz2 ") reinstalled. Here I get the following output: ------------- snip --------------------------------------- ... NOTE: package tar-replacement-native-1.26-r0: task do_populate_sysroot: Started NOTE:
package tar-replacement-native-1.26-r0: task do_populate_sysroot:
Succeeded NOTE: Tasks Summary: Attempted 126 tasks of which 0 didn't need to be rerun and 0 failed. /Yocto/yocto/scripts/bitbake: Zeile 95:
29888 Speicherzugriffsfehler PSEUDO_BINDIR=$PSEUDOBINDIR PSEUDO_LIBDIR=$PSEUDOBINDIR/../lib/pseudo/lib PSEUDO_PREFIX=$PSEUDOBINDIR/../../ PSEUDO_DISABLED=1 $PSEUDOBINDIR/pseudo $BITBAKE $@

------------- snap ---------------------------------------

From a gdb session (evaluation of the core dump) of the nightly build I get the following output:
------------- snip ---------------------------------------
...
Core was generated by `python /Yocto/yocto/bitbake/bin/bitbake -r conf/hob-pre.conf -R conf/hob-post.c'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f0254626c9e in gdk_window_enable_synchronized_configure ()
from /usr/lib64/libgdk-x11-2.0.so.0
(gdb)
------------- snap ---------------------------------------

The error occurred in each case at the first attempt after a new installation. Commands: ------------- snip --------------------------------------- source oe-init-build-env hob ------------- snap ---------------------------------------

Quoted 7 lines

Changes in "local.conf":

------------- snip --------------------------------------- MACHINE ?= "atom-pc"
------------- snap ---------------------------------------

Is it a bug, or a beginner's mistake?

This seems a pygtk bug of bitbake that only appears on some Linux distribution?
In my Ubuntu 11.04, I don't get the SegFault.

Thanks,
-- Dexuan