[Skyeye-developer] how do your developers debug skyeye?

kang shuo blackfin.kang at gmail.com
Tue Jul 3 10:12:04 CST 2007


On 6/29/07, Gavin Mu <gavin.mu at gmail.com> wrote:
> hello everyone,
>
> I compiled skyeye 1.2.3 on my machine, but I can't run several
> testcases in skyeye-testsuite-2.2. In many times the skyeye stopped at
> "Loaded RAM   ./initrd_old.img" and so on.
Which testcase? I will test them again on my linux box.
> My question is, how your developers know where is the problem? just
> put printf() in source code? I can't find any debug switch in source
Probably we need to add some debug switch to indicate some useful info
for developers. Now we use gdb to debug SkyEye just like to debug
other application of linux.
> code, and I also try to use log function in skyeye.conf, but the log
> is difficult to understand.
log function is to indicate the whole instruction execution path at
runtime.You can get some idea from it about what is your program
execution trace and where it halted?
>
> --
> 穆立超(Gavin Mu)
> Beijing University of Posts and Telecommunications
>
> _______________________________________________
> Skyeye-developer mailing list
> Skyeye-developer at lists.gro.clinux.org
> http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
>
>



More information about the Skyeye-developer mailing list