unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: RenéKöcher <shirk87@gmail.com>
To: guile-devel@gnu.org
Subject: Re: guile-1.8 and goops c-api
Date: Wed, 20 Feb 2008 21:22:40 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080220T210957-127@post.gmane.org> (raw)
In-Reply-To: f52e27170802200153o45a3f819o3b6b1a7d527319f9@mail.gmail.com

Sorry to reply to myself but I detected the problem.
My code is correct and working as expected but scm_add_slot()
will segfault anyways because of bug #22369.
 
I checked it agianst the present cvs head and it still an issue.
Applying the supplied patch fixes the problem.
In existing code the same behavior can be achieved by a local copy
of scm_add_slot with an additional SCM_UNDEFINED.

Greetings
Shirk

 ----------------------------------------------------------------------
 BitSpinn.org  - Don't get twisted up!
----------------------------------------------------------------------
 









      reply	other threads:[~2008-02-20 21:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20  9:53 guile-1.8 and goops c-api René Köcher
2008-02-20 21:22 ` RenéKöcher [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=loom.20080220T210957-127@post.gmane.org \
    --to=shirk87@gmail.com \
    --cc=guile-devel@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).