[ECOS] where trace and assert run?

[ECOS] where trace and assert run?

[张 亮]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 903 bytes --]


All,
  I have debug my application in i386-elf-gdb(host-pc target),every time,a 
*.stackdump file will created,I guess it is the trace instuments provided 
by ecos that did it,but i do not know its machanism.questions are:
  since trace code was run in target,so  who created this file in 
host???and how trace running in target write this file through serial 
port??    
  because target pc  maybe do not support filesystem,So i guess like this:
program running on target send "create file and write file" command to host 
then i386-elf-gdb execute this command.

Brs/johnsonest



_________________________________________________________________
ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/lccn/ 


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] where trace and assert run?

[Jonathan Larmour]

? ? wrote:
> 
> All,
>  I have debug my application in i386-elf-gdb(host-pc target),every 
> time,a *.stackdump file will created,I guess it is the trace instuments 
> provided by ecos that did it,but i do not know its machanism.questions are:
>  since trace code was run in target,so  who created this file in 
> host???

That's nothing to do with eCos. Are you sure it was from GDB at all? I'm 
sure the contents might indicate what generated it!

Jifl
-- 
eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss