Re: [ECOS] Stress testing JFFS2

[Andrew Lunn <andrew@lunn.ch>]

On Tue, Oct 07, 2003 at 06:45:57PM +0200, Thomas Koeller wrote:
> I also wrote a test program (attached) that runs on my target
> hardware as well as the synth target. The only thing that's special
> about it is that main() must be called from initialization context,
> it wants to start the scheduler itself.

What do you mean by this last bit? 

Also, you said this works for synth? Its segment faulting for me.....

Round #14
Opened existing file '/jffs2/file_0008'
Checking contents...OK
Overwriting existing file '/jffs2/file_0008' with 11654 data bytes
Duration = 0 seconds
Round #15
Creating new file '/jffs2/file_0006' of size 3714
Wrote 3714 bytes to file '/jffs2/file_0006'
Duration = 0 seconds
Round #16
Creating new file '/jffs2/file_0007' of size 30091
Wrote 30091 bytes to file '/jffs2/file_0007'
Duration = 0 seconds
Round #17
Creating new file '/jffs2/file_0000' of size 235667
iput called for used inode
iput called for used inode
iput called for used inode
iput called for used inode
iput called for used inode
iput called for used inode
iput called for used inode
Wrote 235667 bytes to file '/jffs2/file_0000'
Duration = 0 seconds
Round #18
Creating new file '/jffs2/file_0005' of size 60276
read_cache_page
 
Program received signal SIGSEGV, Segmentation fault.
0x0101fd12 in rb_erase (elm=0x380097, head=0x2029968)
    at /home/lunn/eCos/anoncvs/packages/compat/linux/current/src/rbtree.c:281
281                             elm = left;

Now this assignment looks strange. I don't see how this can cause a
sigfault.

Please could you run it with the latest CVS on your synth target. Im
wondering if i have a compiler problem. I've got gcc 3.3.2 installed
on my Debian-testing system.


   Thanks
      Andrew

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