Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Crasher bug in infptrace.c
Date: Mon, 31 Dec 2001 22:05:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1020101075824.20869D-100000@is> (raw)
In-Reply-To: <3C30C416.2939@redhat.com>


On Mon, 31 Dec 2001, Michael Snyder wrote:

> > > (FWIW, 1MB is too large for DJGPP, whose runtime stack defaults to
> > > 512KB.  `getrlimit' is supported, so it will tell.)
> > 
> > Does djgpp use infptrace?
> 
> And I meant to add -- if so, you can always define GDB_MAX_ALLOCA
> to a smaller value.

Having yet another system-dependent macro is something I wanted to avoid.

Also, a static compile-time limit would have trouble in the face of users 
and sysadmins who can change the stack limits with `ulimit' and similar 
facilities.  Even with DJGPP, you can modify the maximum stack size of a 
program to an arbitrarily large or small value with a special utility.

Perhaps setting the limit you suggested to a much smaller value, like 
10KB, say, would be a better and easier way of solving this.  IIRC, last 
time the alloca issue was discussed, the consensus about the maximum size
of safe off-stack allocations was that it should be a few KB.


  reply	other threads:[~2002-01-01  6:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-30 16:25 Michael Snyder
2001-12-30 22:26 ` Eli Zaretskii
2001-12-31 12:03   ` Michael Snyder
2001-12-31 12:05     ` Michael Snyder
2001-12-31 22:05       ` Eli Zaretskii [this message]
2001-12-31 21:59     ` Eli Zaretskii
2002-01-02 22:26 ` Andrew Cagney
2002-01-03 11:27   ` Michael Snyder
2002-01-03 11:58     ` Andrew Cagney
2002-01-03 12:15       ` Michael Snyder
2002-01-13 17:48         ` Andrew Cagney
2002-01-13 18:41           ` Michael Snyder
2002-01-13 19:27             ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.SUN.3.91.1020101075824.20869D-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox