Op woensdag 1 juli 2015 13:53:47 schreef Alexander Graf: > On 30.06.15 17:43, Freek de Kruijf wrote: > > Op dinsdag 30 juni 2015 11:49:09 schreef u: > >> On 06/30/15 11:24, Freek de Kruijf wrote: > >>> Op dinsdag 30 juni 2015 10:57:31 schreef Alexander Graf: > >>>> On 06/30/15 10:55, Freek de Kruijf wrote: > >>>>> Earlier a second boot of a system generated with this build for > >>>>> Raspberry > >>>>> Pi 1B did not work. Now I have a system that works and can be booted > >>>>> again. > >>>>> > >>>>> However trying to start a module with yast (ncurses), I tried network, > >>>>> software repositories and software all end in the following error > >>>>> message: > >>>>> > >>>>> /sbin/yast: line 426: 19947 Segmentation fault $ybindir/y2base > >>>>> $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS > >>>>> > >>>>> However 19947 in the above message differs with the type of module > >>>>> called > >>>>> and with the locale used. > >>>>> > >>>>> The repository still does not contain the ruby 2.2 modules for > >>>>> libstorage. > >>>>> I build these modules, which went OK. I noticed gcc5 was used. > >>>>> > >>>>> I will continue with this build to configure the applications I use. > >>>> > >>>> Do you think you could gdb the y2base binary to figure out where > >>>> exactly > >>>> it segfaults? > >>> > >>> Alex, I have no experience with gdb. I know it is used to debug and one > >>> can > >>> set breakpoints and step through the code, but that's all I know. > >> > >> No worries, there's always a first time :). In this case, all we need is > >> to attach to the program and then do 'bt' when we see the segfault. > >> > >>> I tried to run yast in one console and did "gdb -p process-id" in > >>> another > >>> after installing yast2-core-debugger. However it likes to have > >>> yast2-core- > >>> debuginfo which is not available. After giving a c in gdb and selecting > >>> software in the ncurses console, gdb continues with the following > >>> output: > >>> > >>> (gdb) c > >>> Continuing. > >>> Detaching after fork from child process 20159. > >>> [Thread 0xb601f450 (LWP 20077) exited] > >>> [Thread 0xb631b450 (LWP 20076) exited] > >>> [Inferior 1 (process 20075) exited normally] > >> > >> This means that the process was doing just fine, no segfault. So maybe a > >> different PID was the one broken? Which PID did you attach to? According > >> to the log, "y2base" is the application that faults. > >> > >> If you can't find it, try to attach strace -f to the yast binary to > >> figure out which binary gets executed. The strace should also at least > >> print out which PID segfaulted. > > > > Attached you will find strace.2. I can't find anything about a segfault. > > Search for this line: > > [pid 25753] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, > si_addr=0x10} --- > > That's where the segfault occurs :).
I entered the following bug in bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=936788 The problem is apparently in the package yast2-pkg-bindings. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org