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

[kang shuo]

On 7/6/07, Gavin Mu <gavin.mu at gmail.com> wrote:
> 2007/7/3, kang shuo <blackfin.kang at gmail.com>:
> > 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.
> for example, this:
> gavin at gavin:~/embeded/skyeye-testsuite-2.2/u-boot/mpc8560$ skyeye
>
> **************************** WARNING **********************************
> If you want to run ELF image, you should use -e option to indicate
> your elf-format image filename. Or you only want to run binary image,
> you need to set the filename of the image and its entry in skyeye.conf.
> ***********************************************************************
>
> big_endian is false.
> arch: ppc
> mach info: name mpc8560, mach_init addr 0x80be390
> log_info: log is on.
> log_info:log file is uboot.log, fd is 0x80f5228
> log_info: log start clock 1
> log_info: log end clock 200000
> uart_mod:0, desc_in:, desc_out:, converter:
> malloc succ for dpram, dpram=0x80f5470
> TLB missed at 0x0,addr=0x0
Read the following warnning message carefully. You should run skyeye
with "-e" option.

 **************************** WARNING **********************************
 If you want to run ELF image, you should use -e option to indicate
 your elf-format image filename. Or you only want to run binary image,
 you need to set the filename of the image and its entry in skyeye.conf.
 ***********************************************************************



> > > 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
> > >
> > >
> >
> > _______________________________________________
> > Skyeye-developer mailing list
> > Skyeye-developer at lists.gro.clinux.org
> > http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
> >
>
>
> --
> 穆立超(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
>
>