On Tue, Mar 20, 2012 at 12:18 AM, Andreas Müller <[email protected]> wrote: > Hi, > > midori crashes with segmentation fault since a while (0.4.3 & 0.4.4). > To understand why I would like to start a gdb remote debug session. In > the past I prepared the image in the following way to get as much > libraries as possible compiled with -O0 since I do not know which > component might be responsible: > > 1. clean all tmp dirs > 2. build all recipes where -O0 is not wanted > (u-boot/kernel/gdb/gdb-cross) or not possible (eglibc/lttng-ust) > 3. added in local.conf: 'SELECTED_OPTIMIZATION = "${DEBUG_OPTIMIZATION} -O0' > 4. build image > > This sequence does not work anymore since the change in local.conf > causes most (all?) recipes to rebuild which crashes at least at > eglibc. > > I am running a bit out of ideas to get this done. The only solution I > see is a minimum optimization passed in the recipe together with 3. > and build from scratch. > > Comments / better ideas?
[1] should bring back old behavior - thanks Andreas [1] http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2012-March/005842.html _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
