public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: ness <ness@zh.t2-design.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] the problem about the file system
Date: Fri, 08 Sep 2000 01:02:00 -0000	[thread overview]
Message-ID: <00090900011802.00743@Ness> (raw)

    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

             reply	other threads:[~2000-09-08  1:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-08  1:02 ness [this message]
2000-09-10 20:33 ` Jonathan Larmour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00090900011802.00743@Ness \
    --to=ness@zh.t2-design.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).