[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
nano-X crashes on munmap
From: ####@####.#### Date: 11 Jun 2007 16:27:17 +0100 Message-Id: <3A7D4529E8A45F468E97C430CB06F132017E540E@argos2.clb.tcfr.thales> Hi, I'm starting to use nano-X on a Nios II processor runing uClinux. Nano-X seems to crash easily on the error : munmap of non-mmaped memory by process <pid> (nano-X): 85d0000 Actually, it can even crash with only a nxterm without nanowm ! However, a find / grep on the source code doesn't show lot's of use of mmap/munmap. Is the trouble known ? Is there a work-around ? The version I can see in ChangeLog is "0.90". Is there a more recent version ? Thanks a lot, regards, -- Frederic | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] nano-X crashes on munmap
From: "Greg Haerr" ####@####.#### Date: 11 Jun 2007 23:47:40 +0100 Message-Id: <1a3501c7ac7a$7a84ce60$6401a8c0@winXP> : However, a find / grep on the source code doesn't show lot's of use of mmap/munmap. There's munmap is used in drivers/scr_fb.c to unmap the screen memory when quiting, and also used at times in some of the image load/unload routines. I think there's a #define HAVEMAP that can be undefined in include/device.h to use a slower mechanism to read image files. : The version I can see in ChangeLog is "0.90". Is there a more recent version ? 0.91 has been out for a long time and is available on the web site. The CVS version is newer than that, and should be used. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
RE: [nanogui] nano-X crashes on munmap
From: ####@####.#### Date: 13 Jun 2007 17:41:55 +0100 Message-Id: <3A7D4529E8A45F468E97C430CB06F132017E5421@argos2.clb.tcfr.thales> Hi Greg, thank you for this answer. I have modified device.h to define HAVEMAP to 0, but the problem is still there, except that it may occur less often... Actually, I've traced a litle bit the things. When I launch nano-X, scr_fb.c/fb_open() is called and a mmap(addr=0x85e00000,sz=960000) that is performed. Then, I launch nanowm, landmine, and move the application on the screen. After a little time, I can see that : 1> scr_fb.c/fb_close() is called => why ? Nano-X is not supposed to leave there ! 2> the munmap() call, in spite of correct args (addr=0x85e00000,sz=960000), crashes on "munmap of non-mmaped memory..." I may be wrong, but I think that there is a first problem because nano-X should not call fb_close() (*), and a 2d one with the NiosII port of uClinux. 0x85e00000 seems to be a very high address, and I think that in Nios architecture, MSB bit to 1 means uncached memory... (*) I don't know if it is important, but there is a trouble with the mouse pointer to "jump" sometimes. Maybe the coordinates become wrong which causes trouble to nano-X ? Regards, -- Frédéric -----Message d'origine----- De : Greg Haerr ####@####.#### Envoyé : mardi 12 juin 2007 00:47 À : ####@####.#### ####@####.#### Objet : Re: [nanogui] nano-X crashes on munmap : However, a find / grep on the source code doesn't show lot's of use of mmap/munmap. There's munmap is used in drivers/scr_fb.c to unmap the screen memory when quiting, and also used at times in some of the image load/unload routines. I think there's a #define HAVEMAP that can be undefined in include/device.h to use a slower mechanism to read image files. : The version I can see in ChangeLog is "0.90". Is there a more recent version ? 0.91 has been out for a long time and is available on the web site. The CVS version is newer than that, and should be used. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |