A error from skyeye occur without skyeye.conf in the current directory
a very fast full system simulator
Status: Beta
Brought to you by:
kangsh
Menu
▾
▴
#107 A error from skyeye occur without skyeye.conf in the current directory
When I run skyeye in a directory without skyeye.conf, I got a segmentation fault. The information returned is following:
=============================================================
lyj@lyj-work-upc:~$ cd /
lyj@lyj-work-upc:/$ /opt/skyeye/bin/skyeye -e /opt/skyeye/testsuite/arm_hello/arm_hello SkyEye 1.3.5
SkyEye is an Open Source project under GPL. All rights of different parts or modules are reserved by their author. Any modification or redistributions of SkyEye should not remove or modify the annoucement of SkyEye copyright.
Get more information about it, please visit the homepage http://www.skyeye.org.
Type "help" to get command list.
(skyeye) start
[SkyEye Crashed]. Please report the following output to skyeye-developer@lists.sourceforge.net.
In SIM_start, Should provide valid arch option in your config file.
/opt/skyeye/lib/skyeye/libcommon.so.0(skyeye_log+0x19d) [0x7f554d56df8d]
/opt/skyeye/lib/skyeye/libcommon.so.0(com_start+0x9) [0x7f554d56f149]
/usr/lib/python2.6/lib-dynload/_ctypes.so(ffi_call_unix64+0x4c) [0x7f55414d402c]
/usr/lib/python2.6/lib-dynload/_ctypes.so(ffi_call+0x243) [0x7f55414d3713]
/usr/lib/python2.6/lib-dynload/_ctypes.so(_CallProc+0x394) [0x7f55414ce134]
/usr/lib/python2.6/lib-dynload/_ctypes.so(+0x9a03) [0x7f55414c5a03]
/usr/lib/libpython2.6.so.1.0(PyObject_Call+0x53) [0x7f554cef54e3]
/usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x48e1) [0x7f554cf9a9e1]
/usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5a98) [0x7f554cf9bb98]
(skyeye) q
No valid arch option is provided.
Destroy threads.
Unload all modules.
exit.
=============================================================
I think skyeye should have a error information, and not continue running.
As a private idea, I also think skyeye should find a configuration file in directory with image, such as /opt/skyeye/testsuite/arm_hello, at first.
Because I can load different images comfortably and don't need edit configuration in the current directory before changing the image tested.
That is a critical bug for user. I mark it a high priority.