|
From: Paul A. <pal...@ea...> - 2003-08-27 03:16:57
|
Please explain what you mean. Is it a particular device? (Not all are really tested, I don't have all the chips and in any case didn't exhaustively test everything.) Is it memory access? I do split large memory requests into many smaller ones in a not very efficient manner. Perhaps we have a stack overflow. That would be easy to fix, Instead of if (size>16) return GetMem( 16) || GetMem( size-16) I could do a binary split, or tail recusion, or iterative techniques. Paul On Tue, 2003-08-26 at 21:51, Gregg C Levine wrote: > Hello again from Gregg C Levine > Oh, and yes, and no. Yes, because when I commented it out it compiled > okay, but through an oops instead. I tried an earlier version, and it > through one as well. Its a fuse issue, it seems the loaded module > can't support the paging aspects of the program. > ------------------- > Gregg C Levine han...@wo... > ------------------------------------------------------------ > "The Force will be with you...Always." Obi-Wan Kenobi > "Use the Force, Luke." Obi-Wan Kenobi > (This company dedicates this E-Mail to General Obi-Wan Kenobi ) > (This company dedicates this E-Mail to Master Yoda ) > > > > > -----Original Message----- > > From: Paul Alfille [mailto:pal...@ea...] > > Sent: Tuesday, August 26, 2003 8:35 PM > > To: Gregg C Levine > > Subject: OWFS > > > > Hi Gregg, > > > > Usually, I comment out the line in main.c that calls dfork when I > debug > > so I can see console messages. Is that the problem? > > > > Paul > > > > |