From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Crasher bug in infptrace.c
Date: Mon, 31 Dec 2001 12:05:00 -0000 [thread overview]
Message-ID: <3C30C416.2939@redhat.com> (raw)
In-Reply-To: <3C30C36F.32D5@redhat.com>
Michael Snyder wrote:
>
> Eli Zaretskii wrote:
> >
> > On Sun, 30 Dec 2001, Michael Snyder wrote:
> >
> > > + /* Set an upper limit on alloca. */
> > > + #ifndef GDB_MAX_ALLOCA
> > > + #define GDB_MAX_ALLOCA 0x100000
> > > + #endif
> >
> > Isn't it better to use `getrlimit' to find out the max stack size, than
> > to set up arbitrary limits (and proliferate system-specific definitions
> > of GDB_MAX_ALLOCA)? At least on systems where `getrlimit' is available,
> > I think we should use it.
>
> Good idea, but it will require additional work (such as
> using configure to determine whether getrlimit is supported).
> May I suggest that this patch be accepted until someone
> volunteers to do a better one?
>
> > (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. That's why I included it.
next prev parent reply other threads:[~2001-12-31 20: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 [this message]
2001-12-31 22:05 ` Eli Zaretskii
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=3C30C416.2939@redhat.com \
--to=msnyder@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.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