<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>417</bug_id>
          
          <creation_ts>2010-10-08 23:36:35 +0000</creation_ts>
          <short_desc>gcc compile in sdk image failed with qemuppc</short_desc>
          <delta_ts>2011-02-28 22:32:49 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Meta-yocto</product>
          <component>meta-yocto</component>
          <version>1.0</version>
          <rep_platform>x86</rep_platform>
          <op_sys>ppc</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>780</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.0 M3</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="xianchao zhang">xianchao.zhang</reporter>
          <assigned_to name="Dexuan Cui">dexuan.cui</assigned_to>
          <cc>dexuan.cui</cc>
    
    <cc>jessica.zhang</cc>
    
    <cc>jiajun.xu</cc>
    
    <cc>ke.yu</cc>
    
    <cc>kevin.tian</cc>
    
    <cc>lianhao.lu</cc>
    
    <cc>nitin.a.kamble</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>qing.he</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>sgw</cc>
    
    <cc>xianchao.zhang</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>10274</commentid>
    <comment_count>0</comment_count>
    <who name="xianchao zhang">xianchao.zhang</who>
    <bug_when>2010-10-08 23:36:35 +0000</bug_when>
    <thetext>Testing Env:    
Host: Ubuntu 10.04 LTS
Qemuppc images: sdk from nightly build on autobuilder,
http://autobuilder.pokylinux.org/nightly/20101007-1/

Steps:

1. download the sdk image from autobuilder
2. boot up qemuppc with sdk image
3. run command &apos;gcc test.c -o test&apos;, there will arise the following error:

root@qemuppc:/opt/my_test# gcc test.c -o test
In file included from /usr/include/stdio.h:75:0,
                 from test.c:1:
/usr/include/libio.h:338:1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10301</commentid>
    <comment_count>1</comment_count>
    <who name="Ke Yu">ke.yu</who>
    <bug_when>2010-10-10 22:59:39 +0000</bug_when>
    <thetext>Dexuan is investigate it.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10302</commentid>
    <comment_count>2</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-11 00:04:25 +0000</bug_when>
    <thetext>The bug is somewhat weird: it doesn&apos;t always happen every time:

root@qemuppc:~# cat mytest.c
int main() { return 0; }

root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
&lt;built-in&gt;:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.
root@qemuppc:~# gcc mytest.c
&lt;built-in&gt;:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.
root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
&lt;built-in&gt;:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.
root@qemuppc:~# gcc mytest.c
&lt;built-in&gt;:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.
root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
&lt;built-in&gt;:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.
root@qemuppc:~# gcc mytest.c
&lt;built-in&gt;:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.
root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
&lt;built-in&gt;:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.
root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
root@qemuppc:~# gcc mytest.c
&lt;built-in&gt;:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.
root@qemuppc:~# gcc mytest.c</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10305</commentid>
    <comment_count>3</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-11 01:34:07 +0000</bug_when>
    <thetext>(In reply to comment #2)
&gt; The bug is somewhat weird: it doesn&apos;t always happen every time:
&gt; root@qemuppc:~# cat mytest.c
&gt; int main() { return 0; }

Actually it&apos;s the c preprocessor cpp that gets the SegFault (not every time):

root@qemuppc:~# echo -n &gt; k.c
root@qemuppc:~# /usr/bin/powerpc-poky-linux-cpp  k.c
# 1 &quot;k.c&quot;
# 1 &quot;&lt;built-in&gt;&quot;
# 1 &quot;&lt;command-line&gt;&quot;
# 1 &quot;k.c&quot;
root@qemuppc:~# /usr/bin/powerpc-poky-linux-cpp  k.c
# 1 &quot;k.c&quot;
# 1 &quot;&lt;built-in&gt;&quot;
# 1 &quot;&lt;command-line&gt;&quot;
# 1 &quot;k.c&quot;
root@qemuppc:~# /usr/bin/powerpc-poky-linux-cpp  k.c
# 1 &quot;k.c&quot;
&lt;built-in&gt;:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.

So this is definitely a gcc&apos;s issue.

Dongxiao saild on mips when he upgraded gcc to 4.5, he didn&apos;t see the bug. So looks like something later causes the bug.
I&apos;m trying to locate the culprit commit.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10363</commentid>
    <comment_count>4</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-11 22:30:57 +0000</bug_when>
    <thetext>(In reply to comment #3)
&gt; (In reply to comment #2)
&gt; &gt; The bug is somewhat weird: it doesn&apos;t always happen every time:
&gt; &gt; root@qemuppc:~# cat mytest.c
&gt; &gt; int main() { return 0; }
&gt; Actually it&apos;s the c preprocessor cpp that gets the SegFault (not every time):
&gt; root@qemuppc:~# echo -n &gt; k.c
&gt; root@qemuppc:~# /usr/bin/powerpc-poky-linux-cpp  k.c
&gt; # 1 &quot;k.c&quot;
&gt; # 1 &quot;&lt;built-in&gt;&quot;
&gt; # 1 &quot;&lt;command-line&gt;&quot;
&gt; # 1 &quot;k.c&quot;
&gt; root@qemuppc:~# /usr/bin/powerpc-poky-linux-cpp  k.c
&gt; # 1 &quot;k.c&quot;
&gt; # 1 &quot;&lt;built-in&gt;&quot;
&gt; # 1 &quot;&lt;command-line&gt;&quot;
&gt; # 1 &quot;k.c&quot;
&gt; root@qemuppc:~# /usr/bin/powerpc-poky-linux-cpp  k.c
&gt; # 1 &quot;k.c&quot;
&gt; &lt;built-in&gt;:0:0: internal compiler error: Segmentation fault
&gt; Please submit a full bug report,
&gt; with preprocessed source if appropriate.
&gt; See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.
&gt; So this is definitely a gcc&apos;s issue.
&gt; Dongxiao saild on mips when he upgraded gcc to 4.5, he didn&apos;t see the bug. So
&gt; looks like something later causes the bug.
&gt; I&apos;m trying to locate the culprit commit.

Using the nightly images, I can narrow down to commits of Oct 6:
http://autobuilder.pokylinux.org/nightly/20101005-1/qemu/qemuppc/ is OK, but
http://autobuilder.pokylinux.org/nightly/20101006-1/qemu/qemuppc/ is NOT ok.

I looked at the commits of Oct 5 and Oct6, but didn&apos;t find a culprit commit. :-(</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10370</commentid>
    <comment_count>5</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-12 01:26:48 +0000</bug_when>
    <thetext>(In reply to comment #4)
&gt; Using the nightly images, I can narrow down to commits of Oct 6:
&gt; http://autobuilder.pokylinux.org/nightly/20101005-1/qemu/qemuppc/ is OK, but
&gt; http://autobuilder.pokylinux.org/nightly/20101006-1/qemu/qemuppc/ is NOT ok.
&gt; I looked at the commits of Oct 5 and Oct6, but didn&apos;t find a culprit commit.
A surprising thing is: 
http://autobuilder.pokylinux.org/nightly/20101003-1/qemu/qemuppc/is also NOT ok -- can&apos;t understand why Oct05 is ok... looks there is some kind of tricky thing?

I tried gdb inside the target qempppc, but what&apos;s odd is: gdb can&apos;t catch the &quot; Segmentation fault&quot; the target ppc&apos;s cpp reports.
strace also doesn&apos;t show useful info.

gcc 4.5 was upgraded for ppc on Sep 22. I had a look at all the commits after  that, but didn&apos;t find an obvious suspecct. glibc-&gt;eglibc might be one and I&apos;ll be trying that.

BTW: I also looked at gcc&apos;s bugzilla and didn&apos;t find similar bugs.

Currently I&apos;m buiding qemuppc based on today&apos;s latest master and hope I can reproduce the issue on it and try to get new findings.

Could somebody give some hints? Thanks!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10395</commentid>
    <comment_count>6</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-12 17:37:15 +0000</bug_when>
    <thetext>(In reply to comment #5)
&gt; (In reply to comment #4)
&gt; &gt; Using the nightly images, I can narrow down to commits of Oct 6:
&gt; &gt; http://autobuilder.pokylinux.org/nightly/20101005-1/qemu/qemuppc/ is OK, but
&gt; &gt; http://autobuilder.pokylinux.org/nightly/20101006-1/qemu/qemuppc/ is NOT ok.
&gt; &gt; I looked at the commits of Oct 5 and Oct6, but didn&apos;t find a culprit commit.
&gt; A surprising thing is: 
&gt; http://autobuilder.pokylinux.org/nightly/20101003-1/qemu/qemuppc/is also NOT ok
&gt; -- can&apos;t understand why Oct05 is ok... looks there is some kind of tricky
&gt; thing?
&gt; I tried gdb inside the target qempppc, but what&apos;s odd is: gdb can&apos;t catch the &quot;
&gt; Segmentation fault&quot; the target ppc&apos;s cpp reports.
&gt; strace also doesn&apos;t show useful info.
&gt; gcc 4.5 was upgraded for ppc on Sep 22. I had a look at all the commits after 
&gt; that, but didn&apos;t find an obvious suspecct. glibc-&gt;eglibc might be one and I&apos;ll
&gt; be trying that.
&gt; BTW: I also looked at gcc&apos;s bugzilla and didn&apos;t find similar bugs.
&gt; Currently I&apos;m buiding qemuppc based on today&apos;s latest master and hope I can
&gt; reproduce the issue on it and try to get new findings.
Unfortunately, I can NOT reproduce the issue on (yesterday&apos;s) latest master (commit 04ace838). :-(  Looks I&apos;ll have to try to further look into the old &quot;buggy&quot; nightly images.


Thanks,
-- Dexuan</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10409</commentid>
    <comment_count>7</comment_count>
    <who name="xianchao zhang">xianchao.zhang</who>
    <bug_when>2010-10-12 21:18:42 +0000</bug_when>
    <thetext>(In reply to comment #0)
&gt; Testing Env:    
&gt; Host: Ubuntu 10.04 LTS
&gt; Qemuppc images: sdk from nightly build on autobuilder,
&gt; http://autobuilder.pokylinux.org/nightly/20101007-1/
&gt; 
&gt; Steps:
&gt; 
&gt; 1. download the sdk image from autobuilder
&gt; 2. boot up qemuppc with sdk image
&gt; 3. run command &apos;gcc test.c -o test&apos;, there will arise the following error:
&gt; 
&gt; root@qemuppc:/opt/my_test# gcc test.c -o test
&gt; In file included from /usr/include/stdio.h:75:0,
&gt;                  from test.c:1:
&gt; /usr/include/libio.h:338:1: internal compiler error: Segmentation fault
&gt; Please submit a full bug report,
&gt; with preprocessed source if appropriate.
&gt; See &lt;http://gcc.gnu.org/bugs.html&gt; for instructions.

With the milestone build 10/11, this issue has not arise. seems fixed?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10410</commentid>
    <comment_count>8</comment_count>
    <who name="Jessica">jessica.zhang</who>
    <bug_when>2010-10-12 21:22:06 +0000</bug_when>
    <thetext>It&apos;s not fixed but as Dexuan mentioned can&apos;t be reproduced with the latest build.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10461</commentid>
    <comment_count>9</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-13 20:21:45 +0000</bug_when>
    <thetext>(In reply to comment #6)
&gt; (In reply to comment #5)
&gt; &gt; (In reply to comment #4)
&gt; &gt; &gt; Using the nightly images, I can narrow down to commits of Oct 6:
&gt; &gt; &gt; http://autobuilder.pokylinux.org/nightly/20101005-1/qemu/qemuppc/ is OK, but
&gt; &gt; &gt; http://autobuilder.pokylinux.org/nightly/20101006-1/qemu/qemuppc/ is NOT ok.
&gt; &gt; &gt; I looked at the commits of Oct 5 and Oct6, but didn&apos;t find a culprit commit.
&gt; &gt; A surprising thing is: 
&gt; &gt; http://autobuilder.pokylinux.org/nightly/20101003-1/qemu/qemuppc/is also NOT ok
&gt; &gt; -- can&apos;t understand why Oct05 is ok... looks there is some kind of tricky
&gt; &gt; thing?
&gt; &gt; I tried gdb inside the target qempppc, but what&apos;s odd is: gdb can&apos;t catch the &quot;
&gt; &gt; Segmentation fault&quot; the target ppc&apos;s cpp reports.
&gt; &gt; strace also doesn&apos;t show useful info.
&gt; &gt; gcc 4.5 was upgraded for ppc on Sep 22. I had a look at all the commits after 
&gt; &gt; that, but didn&apos;t find an obvious suspecct. glibc-&gt;eglibc might be one and I&apos;ll
&gt; &gt; be trying that.
&gt; &gt; BTW: I also looked at gcc&apos;s bugzilla and didn&apos;t find similar bugs.
&gt; &gt; Currently I&apos;m buiding qemuppc based on today&apos;s latest master and hope I can
&gt; &gt; reproduce the issue on it and try to get new findings.
&gt; Unfortunately, I can NOT reproduce the issue on (yesterday&apos;s) latest master
&gt; (commit 04ace838). :-(  Looks I&apos;ll have to try to further look into the old
&gt; &quot;buggy&quot; nightly images.

With Qing&apos;s great help (previously gdb can&apos;t catch the SIGSEGV of cpp, Qing uses the LD_PRELOAD trick to work this around and can catch the signal now -- my understanding is: Qing re-sets the signal handling of the signal in an own .so), we managerd to use gdb to get the place where the SegFault happens:

Loaded symbols for /lib/ld.so.1
Core was generated by `/usr/libexec/gcc/powerpc-poky-linux/4.5.0/cc1 -E -quiet -D__unix__ -D__gnu_linu&apos;.
Program terminated with signal 11, Segmentation fault.
#0  0x1099de88 in ?? ()
(gdb) bt
#0  0x1099de88 in ?? ()
#1  0x101bc3b4 in mul_double_with_sign ()
#2  0x101c055c in int_const_binop ()

Due to the lackness of furthe debug info, looks it&apos;s hard to further debug. :-(

disassembing the faulting IP 0x1099de88 shows ppc-specific code. Qing helped to guess a register mighe be clobbered somehow...

BTW: using my build, I can&apos;t reproduce the bug on latest master and builds/milestone.
I tried nightly images: the images of Sep 25~Oct1, Oct 5, Oct8 are ok, while Oct 3, Oct6 and Oct are bad (Unluckily autobuild didn&apos;t save enought debug info). Looks nobody met with the issue in own build...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10462</commentid>
    <comment_count>10</comment_count>
    <who name="Jessica">jessica.zhang</who>
    <bug_when>2010-10-13 20:46:45 +0000</bug_when>
    <thetext>Thanks for the update and hard work on trying to root cause the issue.  I&apos;d say let&apos;s put the bug on the back-burner till we can reproduce it again.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10463</commentid>
    <comment_count>11</comment_count>
    <who name="Qing He">qing.he</who>
    <bug_when>2010-10-13 21:02:50 +0000</bug_when>
    <thetext>(In reply to comment #9)
&gt; previously gdb can&apos;t catch the SIGSEGV of cpp, Qing
&gt; uses the LD_PRELOAD trick to work this around and can catch the signal now --
&gt; my understanding is: Qing re-sets the signal handling of the signal in an own
&gt; .so), we managerd to use gdb to get the place where the SegFault happens:

explain here a little for further reference:
cc1 (which is finally called by cpp/gcc and do most of the work) has a signal handler of its own to intercept SIGSEGV, that means it bypassed normal signal handling and there won&apos;t be a core file dumped on segfault.

The trick is to replace the signal() function (using LD_PRELOAD) so the action of setting own handler of cc1 is ignored.

---
$ cat &gt; b.c &lt;&lt;EOF
typedef void (*sighandler_t)(int);
sighandler_t signal(int sig, sighandler_t handler) {return handler;}
EOF

$ gcc b.c -o b.so -shared
$ LD_PRELOAD=./b.so cpp a.c</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10470</commentid>
    <comment_count>12</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-13 21:53:06 +0000</bug_when>
    <thetext>(In reply to comment #10)
&gt; Thanks for the update and hard work on trying to root cause the issue.  I&apos;d say
&gt; let&apos;s put the bug on the back-burner till we can reproduce it again.

We have asked Scott to save more debug info in the next builds.
At present let&apos;s keep a close eye on the new builds and see if autobuilder can reproduce the issue again.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10689</commentid>
    <comment_count>13</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-20 00:38:09 +0000</bug_when>
    <thetext>(In reply to comment #12)
&gt; (In reply to comment #10)
&gt; &gt; Thanks for the update and hard work on trying to root cause the issue.  I&apos;d say
&gt; &gt; let&apos;s put the bug on the back-burner till we can reproduce it again.
&gt; We have asked Scott to save more debug info in the next builds.
&gt; At present let&apos;s keep a close eye on the new builds and see if autobuilder can
&gt; reproduce the issue again.

I still can&apos;t reproduce the issue on recent nightly builds, like builds of Oct 11, 18:
http://autobuilder.pokylinux.org/milestone/20101011/qemu/qemuppc/
http://autobuilder.pokylinux.org/milestone/20101018/qemu/qemuppc/
So looks this bug was somehow hidden or fixed?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10803</commentid>
    <comment_count>14</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-26 23:15:10 +0000</bug_when>
    <thetext>(In reply to comment #13)
&gt; (In reply to comment #12)
&gt; &gt; (In reply to comment #10)
&gt; &gt; &gt; Thanks for the update and hard work on trying to root cause the issue.  I&apos;d say
&gt; &gt; &gt; let&apos;s put the bug on the back-burner till we can reproduce it again.
&gt; &gt; We have asked Scott to save more debug info in the next builds.
&gt; &gt; At present let&apos;s keep a close eye on the new builds and see if autobuilder can
&gt; &gt; reproduce the issue again.
&gt; I still can&apos;t reproduce the issue on recent nightly builds, like builds of Oct
&gt; 11, 18:
&gt; http://autobuilder.pokylinux.org/milestone/20101011/qemu/qemuppc/
&gt; http://autobuilder.pokylinux.org/milestone/20101018/qemu/qemuppc/
&gt; So looks this bug was somehow hidden or fixed?

Still can not reproduce the issue on recent builds:
http://autobuilder.pokylinux.org/milestone/20101024/qemu/qemuppc/</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10902</commentid>
    <comment_count>15</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-11-15 01:05:01 +0000</bug_when>
    <thetext>(In reply to comment #14)
&gt; (In reply to comment #13)
&gt; &gt; (In reply to comment #12)
&gt; &gt; &gt; (In reply to comment #10)
&gt; &gt; &gt; &gt; Thanks for the update and hard work on trying to root cause the issue.  I&apos;d say
&gt; &gt; &gt; &gt; let&apos;s put the bug on the back-burner till we can reproduce it again.
&gt; &gt; &gt; We have asked Scott to save more debug info in the next builds.
&gt; &gt; &gt; At present let&apos;s keep a close eye on the new builds and see if autobuilder can
&gt; &gt; &gt; reproduce the issue again.
&gt; &gt; I still can&apos;t reproduce the issue on recent nightly builds, like builds of Oct
&gt; &gt; 11, 18:
&gt; &gt; http://autobuilder.pokylinux.org/milestone/20101011/qemu/qemuppc/
&gt; &gt; http://autobuilder.pokylinux.org/milestone/20101018/qemu/qemuppc/
&gt; &gt; So looks this bug was somehow hidden or fixed?
&gt; Still can not reproduce the issue on recent builds:
&gt; http://autobuilder.pokylinux.org/milestone/20101024/qemu/qemuppc/

Now I can reproduce the issue in latest nightly images (about ~50% probability):
http://autobuilder.pokylinux.org/nightly/20101113-1/qemu/qemuppc/
We have to figiure it out!

BTW: looks it&apos;s related to ldconfig:
After running ldconfig in target, I can&apos;t reproduce the issue any longer.

I&apos;m trying to figure out what causes the occasional SegFault.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12104</commentid>
    <comment_count>16</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2011-02-24 22:54:11 +0000</bug_when>
    <thetext>I tried the images http://autobuilder.pokylinux.org/nightly/ and I can&apos;t reproduce the issue any longer.

The last time I reproduced the issue was about 3.5 months ago and since then we did many big changes to Poky. 
I think the issue might somehow become even more difficult to occur even if it hasn&apos;t been fixed. 

So let me mark the bug as WORKSFORME.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12105</commentid>
    <comment_count>17</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2011-02-24 22:55:41 +0000</bug_when>
    <thetext>(In reply to comment #16)
&gt; I tried the images http://autobuilder.pokylinux.org/nightly/ and I can&apos;t
&gt; reproduce the issue any longer.
&gt; The last time I reproduced the issue was about 3.5 months ago and since then we
&gt; did many big changes to Poky. 
&gt; I think the issue might somehow become even more difficult to occur even if it
&gt; hasn&apos;t been fixed. 
&gt; So let me mark the bug as WORKSFORME.

So let me mark the bug as WORKSFORME.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12178</commentid>
    <comment_count>18</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2011-02-28 22:30:37 +0000</bug_when>
    <thetext>Looks we do have a rather tricky and hard-to-reproduce bug on ppc here..
Till now, I haven&apos;t reproduced it locally.
I even tried to manually build ppc on autobuilder, but still couldn&apos;t reproduce it.
However, autobuilder ppc images still have the issue *occassionally*, and with a &quot;bad&quot; image, I estimiate we have a 30%~50% probability to reproduce the issue.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12179</commentid>
    <comment_count>19</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2011-02-28 22:32:49 +0000</bug_when>
    <thetext>(In reply to comment #18)
&gt; Looks we do have a rather tricky and hard-to-reproduce bug on ppc here..
&gt; Till now, I haven&apos;t reproduced it locally.
&gt; I even tried to manually build ppc on autobuilder, but still couldn&apos;t reproduce
&gt; it.
&gt; However, autobuilder ppc images still have the issue *occassionally*, and with
&gt; a &quot;bad&quot; image, I estimiate we have a 30%~50% probability to reproduce the
&gt; issue.

Bug 780 is a duplicate of this one.

*** This bug has been marked as a duplicate of bug 780 ***</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>