public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Earl S. Harris, Jr." <esharris@mitre.org>
To: David Edelsohn <dje@watson.ibm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Catching stack overflow errors
Date: Mon, 07 Aug 2000 05:44:00 -0000	[thread overview]
Message-ID: <398EAF45.57B340A5@mitre.org> (raw)
In-Reply-To: <200008042104.RAA06398@mal-ach.watson.ibm.com>

David Edelsohn wrote:
> 
> >>>>> "Earl S Harris, Jr " writes:
> 
> Earl> Is there a machine independent way to catch stack overflow errors?
> 
> Earl> When I build a recursive program, I want to check if there is stack
> Earl> overflow.
> Earl> I have some solutions that work in one architecture, but not another.
> 
>         Some members of IBM's Tokyo Research Lab have been investigating a
> machine-independent change to GCC that would generate code to check for
> stack overflow / corruption / smashing.  They currently are judging
> community interest to determine if they should try to contribute this code

I think this is important if the following conditions hold.

1. A programmer wants to use non tail recursion in his/her C++ program.
2. He/she doesn't want the program to crash inelegantly.

Earl Harris Jr.

> to GCC.  They have a research report on an external website, but the HTML
> generates a server error at the moment.
> 
> David

  reply	other threads:[~2000-08-07  5:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-04 13:42 Earl S. Harris, Jr.
2000-08-04 14:04 ` David Edelsohn
2000-08-07  5:44   ` Earl S. Harris, Jr. [this message]
2000-08-11  6:30     ` Anthony Green
2000-08-11 15:57       ` Geoff Keating
2000-08-13 13:45 Geert Bosch

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=398EAF45.57B340A5@mitre.org \
    --to=esharris@mitre.org \
    --cc=dje@watson.ibm.com \
    --cc=gcc@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).