 | | malloc() bug found -- BAD MEMORY REGION :-(
|
|
It looks like it's not a bug in legOS, but in the RCX hardware: Memory from 0xfb80 to 0xfd7f is simply NOT WRITEABLE, or more exactly, always read as 0xff, at least on my RCX ! Try the following little test: // // memory test // #include <conio.h> (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) made some tests, and - Yep, it works ! I'd strongly encourage everybody experiencing strange hangups to apply the little fix to mm_init() i suggested. For me, it makes malloc() and dll work perfectly. BTW, there are some minor flaws in dll[x], (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) Great! (...) This has always been a problem- it was an issue with firmdl before dll. Nothing serious, so it was never fixed. (...) You've actually had programs that large? Wow. -Luis (trying to make this more than a one-sided conversation...) (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) My hangups are gone too! Danke! Jürgen (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
Great! Well done, Martin! Toni "Martin Cornelius" <Martin.Cornelius@t-online.de> wrote in message news:38BDC2FD.85668C...line.de... (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) I'm afraid this made no difference for me. I still get dll crashes. My particular symptom is that if I make a 1 line change to legOS then download it, it crashes straight away at the next dll. Even if I undo the change, then rebuild & download (...) (25 years ago, 3-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) the fix only helps for problems that arise when memory is nearly used up, and malloc() tries to use memory above the 'macic' 0xfb80 limit. - Just to make sure: (i have been caught in this trap) -- have you rebuilt your dll application against (...) (25 years ago, 6-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) Yup, did that. I've applied the following fixes to the kernel 0.2.3. Are there any I've missed? . The malloc() bug we've been discussing. . The tx_sem fix for lnp*.c . The memcpy assembler bug. I'm using gcc 2.95.2 & binutils 2.9. Can anyone (...) (25 years ago, 6-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) i vaguely remember this patch was necessary to get gcc-2.95.x to work, but somehow lost the patch. Therefore, i'm still working with egcs-1.1.2. Maybe that's the difference ? Could you tell me where to find the patch ? thanks, Martin. (25 years ago, 7-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) Hi Martin: Its right here "(URL) try rebuild legOS with egcs-1.1.2, then diff the kernel assembler listings. Watch this space... (25 years ago, 7-Mar-00, to lugnet.robotics.rcx.legos)
|
