Bug 1119 - LSB 4.1: glib_threads error
Summary: LSB 4.1: glib_threads error
Status: RESOLVED WONTFIX
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.0-alpha
Hardware: mpc8315e-rdb ppc
: Medium normal
Target Milestone: 1.1 M3
Assignee: Xiaofeng Yan
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-05-27 05:01 UTC by Xiaofeng Yan
Modified: 2011-08-19 01:45 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Xiaofeng Yan 2011-05-27 05:01:27 UTC 
/glib-t2c/tests/glib_threads/glib_threads 36 	unresolved 	
Message from the test:

Target interface(s):
 g_static_rw_lock_reader_trylock
--------
Checked requirement: {g_static_rw_lock_reader_trylock.01.02}
Child process was terminated by signal 6.
Abnormal child process termination. errno: 22.
Comment 1 Xiaofeng Yan 2011-05-27 05:02:09 UTC 
I record this bug and fix it on 1.1
Comment 2 Xiaofeng Yan 2011-07-28 23:21:27 UTC 
Known problem
http://bugs.linuxbase.org/show_bug.cgi?id=3253
Comment 3 Xiaofeng Yan 2011-07-28 23:46:53 UTC 
(In reply to comment #2)
> Known problem
> http://bugs.linuxbase.org/show_bug.cgi?id=3253

Known problem
http://bugs.linuxbase.org/show_bug.cgi?id=3042
Comment 4 Xiaofeng Yan 2011-07-29 01:16:33 UTC 
Known problem
Comment 5 Xiaofeng Yan 2011-08-14 21:28:23 UTC 
This bug could happen occasionally, hardware could cause "Child process was terminated by signal 6" because of the limitation of hardware from mpc8315e. if this bug happen when running lsb suite in your side. You can run test.c from  http://bugs.linuxbase.org/show_bug.cgi?id=3042 manually. if the result is no problem, then this test item should pass lsb test.
Comment 6 Yi Zhao 2011-08-19 01:45:25 UTC 
With 1.1 M3 build on mpc8315e-rdb, this issue doesn't happen.