On 04/22/2015 10:41 AM, HAN wrote: > Hello, > > Since I'm not good at english, so I can make some mistakes. > > This is HAN who studies Android Lollipop developing. > When my custom Lollipop image is downloaded and boot firstly, I got an > issue at libselinux.so and libpcre.so. > > I've got segmentation fault as below. > I guess this segfault came from when SELinux was labelling some packages. > > I've done debug as below backtrace. > It says the segfault was started from pcre_exec.c(line 6844). > > *#Debug Info > *0000000000012ae0 : android/external/pcre/dist/pcre_exec.c:6844 > Link -> > http://androidxref.com/5.1.0_r1/xref/external/pcre/dist/pcre_exec.c#6844 > 000000000000ba20 : android/external/libselinux/src/label_file.c:636 > Link -> > http://androidxref.com/5.1.0_r1/xref/external/libselinux/src/label_file.c#636 > 000000000000ae48 : android/external/libselinux/src/label.c:102 > Link -> > http://androidxref.com/5.1.0_r1/xref/external/libselinux/src/label.c#102 > 000000000000e440 : android/external/libselinux/src/android.c:1134 > Link -> > http://androidxref.com/5.1.0_r1/xref/external/libselinux/src/android.c#1134 > 000000000000ebcc : android/external/libselinux/src/android.c:1213 > Link -> > http://androidxref.com/5.1.0_r1/xref/external/libselinux/src/android.c#1213 > > This issue appeared only one time and I wanted to add some debug logs. > so I've tried to reproduce over 20 times,it doesn't appear though. > > Is there any idea which part should I look at?
I don't see any way we could have triggered that without memory corruption. You mentioned that you are using a custom Lollipop image; what have you modified? If you can reproduce it, then it would be interesting to get more information about the arguments to pcre_exec(). _______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
