 | | Re: problems with creating arrays of larger sizes —Michael Obenland
|
| | | (...) > (...) Who knows. Unless you show your code... Regards, Michael (21 years ago, 14-May-04, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: problems with creating arrays of larger sizes —Andreas Jurk
|
| | | | OK, here is my code. #include <dmotor.h> #include <dsensor.h> #include <unistd.h> #include <dbutton.h> #include <conio.h> #include <stdio.h> #define n 1000 void verzoegerung(unsigned long zeit) { while(zeit--); } int main() { int i; char c[n]; (...) (21 years ago, 17-May-04, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: problems with creating arrays of larger sizes —Nathan Braun
|
| | | | | (...) Hi Andreas I would suggest, that you instanciate your variable as global, and not within the main() function. Or declare it as static so that the compiler does not try to instanciate it on the stack. The problem could be due to a stack (...) (21 years ago, 17-May-04, to lugnet.robotics.rcx.legos)
|
| | | | | |
| | | | | | Re: problems with creating arrays of larger sizes —Michael Obenland
|
| | | | (...) This won't work for sure. If you look into the kernel sources, DEFAULT_STACK_SIZE gives the value for every user program's stack. Actually, this is 1KByte, if I remeber it right. Your character array will be allocated on the stack and so you (...) (21 years ago, 17-May-04, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | RE: problems with creating arrays of larger sizes —Elizabeth Mabrey
|
| | | | (...) Need to understand the difference how array and pointers are being allocated ... And char is usually one or two bytes, depending on type of procesor; and pointer is usually 4 bytes, unless you go to 64-bit processor ... If you wish to utilize (...) (21 years ago, 18-May-04, to lugnet.robotics.rcx.legos)
|
| | | | |
