public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] the problem about the file system
@ 2000-09-08  1:02 ness
  2000-09-10 20:33 ` Jonathan Larmour
  0 siblings, 1 reply; 2+ messages in thread
From: ness @ 2000-09-08  1:02 UTC (permalink / raw)
  To: ecos-discuss

    Hi, all.
    I downloaded the "fileio" and "RAM filesystem" via the CVS.  I compiled them and builded the tests. And I run them on the mips,it is OK. Then I ported the another RAM filesystem (I writted) like FAT. The  compiling and building tests are all right.But I meet the problem when the program is running.I used the GDB to find why.
The process of running is :
It goes to "cyg_hal_invoke_constructors" .

		void
 		cyg_hal_invoke_constructors(void)
	        {
		    pfunc *p;
 		
		    for (p = &__CTOR_END__[-1]; p >= __CTOR_LIST__; p--)
		        (*p) ();
 		#endif
 		    
		} // cyg_hal_invoke_constructors()
 		
     In the circle it first invokes some initial functions about interruption etc. ,
Then it invoked the "Cyg_Fileio_Init_Class()".

 		
 		Cyg_Fileio_Init_Class::Cyg_Fileio_Init_Class()
		{
		    cyg_fd_init();
		
		    cyg_mtab_init();
 		
		    chdir("/");
		}
 	
   After finishing the "Cyg_Fileio_Init_Class()",it invokes the two macro .

                  Cyg_Mutex mtab_lock[CYGNUM_FILEIO_MTAB_MAX];
                  Cyg_Mutex fstab_lock[CYGNUM_FILEIO_FSTAB_MAX];
 
    Then it goes back to the circle in the "cyg_hal_invoke_constructors".When it continues ,the GDB give the information :

               GDB is unable to find the start of the function at 0x80109598
           and thus can't determine the size of that function's stack frame.
           This means that GDB may be unable to access that stack frame, or
           the frames below it.
               This problem is most likely caused by an invalid program counter or
           stack pointer.
               However, if you think GDB should simply search farther back
           from 0x80109598 for code which looks like the beginning of a
           function, you can increase the range of the search using the `set
           heuristic-fence-post' command.

           Error: Remote communication error: Permission denied.
           putpkt: write failed: Permission denied.
           putpkt: write failed: Permission denied.

    I don't know why? Who can tell me why and how to resolve it?
    Many thinks.

                                                                          ness miao
                                                                          9,8

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [ECOS] the problem about the file system
  2000-09-08  1:02 [ECOS] the problem about the file system ness
@ 2000-09-10 20:33 ` Jonathan Larmour
  0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Larmour @ 2000-09-10 20:33 UTC (permalink / raw)
  To: ness; +Cc: ecos-discuss

ness wrote:
> It goes to "cyg_hal_invoke_constructors" .
> 
[snip] 
>     Then it goes back to the circle in the "cyg_hal_invoke_constructors".When it continues ,the GDB give the information 
[snip]

This should now be fixed in the latest anonymous CVS sources. Try
refreshing.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-09-10 20:33 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-09-08  1:02 [ECOS] the problem about the file system ness
2000-09-10 20:33 ` Jonathan Larmour

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).