From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: David Pirotte <david@altosw.be>
Cc: 37066@debbugs.gnu.org
Subject: bug#37066: Using GOOPS #:allocation #:virtual slot option causes stack overflow
Date: Sun, 18 Aug 2019 23:43:30 +0200 [thread overview]
Message-ID: <20190818234330.0f4bf77d@kompiuter> (raw)
In-Reply-To: <20190818050853.17b31311@capac>
Sorry, I sent a private mail, hope this one will be in the right
place.
On Sun, 18 Aug 2019 05:08:53 -0300
David Pirotte <david@altosw.be> wrote:
> This is not goops bug. The problem occurs because you try to set the
> value of the virtual slot, something you should never do.
Thank you for explaining, I understand it now.
I don't think eating the whole CPU and RAM and segmentation fault is a
good default behavior though. If this is a thing one should never do,
shouldn't Guile throw an error, warning or whatever?
Jan
prev parent reply other threads:[~2019-08-18 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 22:42 bug#37066: Using GOOPS #:allocation #:virtual slot option causes stack overflow Jan
2019-08-18 8:08 ` David Pirotte
2019-08-18 21:43 ` Jan [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190818234330.0f4bf77d@kompiuter \
--to=tona_kosmicznego_smiecia@interia.pl \
--cc=37066@debbugs.gnu.org \
--cc=david@altosw.be \
/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).