On Friday, Oct 31, 2003, at 23:38 US/Eastern, Charles Lepple wrote:
Depending on how much you want to mess with the source, you could
rename the main function to something else, and create a new main
function which does the setrlimit call and then calls the old main
function.
Yes! That solved
On Friday, Oct 31, 2003, at 23:35 US/Eastern, David Brown wrote:
{
int labels[20];
int names[1];
float num[1];
These variables in main are probably the cause of the overflow, not the
static ones. You might just try declaring 'names' and 'num' to be
static, but I wo
On Fri, Oct 31, 2003 at 09:53:38PM -0500, Koen van der Drift wrote:
> Yes, here is a snippet:
>
> static int myarray[20][1]
> static int anotherarray[20][1]
>
> int main (int argc char** argv)
> {
> int labels[20];
> int names[1];
> float num[1];
These variable
On Friday, Oct 31, 2003, at 21:11 US/Eastern, David Brown wrote:
What do you mean by assigning
large arrays? Are they declared at the top level in the C file?
Yes, here is a snippet:
static int myarray[20][1]
static int anotherarray[20][1]
int main (int argc char** argv)
{
int l
On Fri, Oct 31, 2003 at 08:40:10PM -0500, Koen van der Drift wrote:
> Well, I figured out why the program is crashing. The code is assigning
> some very large arrays as a static variables, which are created before
> main() is called. They use all available stack, which causes the crash.
> If I
> Static variables should be on the stack. What do you mean by assigning
I meant: "Static variables should _not_ be on the stack".
Dave
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more prod
On Tuesday, Oct 28, 2003, at 22:47 US/Eastern, Koen van der Drift wrote:
On Tuesday, Oct 28, 2003, at 22:12 US/Eastern, Charles Lepple wrote:
#include /* haven't tried this myself */
#include
#include
#include
struct rlimit rlim;
getrlimit(RLIMIT_STACK, &rlim);
rlim.rlim_cur = RLIM_INFINITY
On Tuesday, Oct 28, 2003, at 22:12 US/Eastern, Charles Lepple wrote:
#include /* haven't tried this myself */
#include
#include
#include
struct rlimit rlim;
getrlimit(RLIMIT_STACK, &rlim);
rlim.rlim_cur = RLIM_INFINITY;
setrlimit(RLIMIT_STACK, &rlim);
Both your solution and Peter's didn't wo
On Tuesday, Oct 28, 2003, at 22:12 US/Eastern, Charles Lepple wrote:
#include /* haven't tried this myself */
#include
#include
#include
struct rlimit rlim;
getrlimit(RLIMIT_STACK, &rlim);
rlim.rlim_cur = RLIM_INFINITY;
setrlimit(RLIMIT_STACK, &rlim);
Thanks, I'll try that. I assume this goe
Koen van der Drift wrote:
Hi,
Two of the programs of the emboss package do not work on Mac OS X
apparently because of the limited stacksize on Mac OS X. For instance,
if I type just 'cirdna' at the prompt, I get an segmentation fault.
However if I type 'unlimit stack' first, the program works
On Tuesday, October 28, 2003, at 08:01 PM, Koen van der Drift wrote:
Is there a way to patch the source so that the user doesn't have to
enter 'unlimit stack' each time?
#include /* haven't tried this myself */
#include
#include
#include
struct rlimit rlim;
getrlimit(RLIMIT_STACK, &rlim);
r
Hi,
Two of the programs of the emboss package do not work on Mac OS X
apparently because of the limited stacksize on Mac OS X. For instance,
if I type just 'cirdna' at the prompt, I get an segmentation fault.
However if I type 'unlimit stack' first, the program works without a
problem.
Is the
12 matches
Mail list logo
