On Mon 07 Feb 2011 13:26, Nigel Warner writes:
> (define (test-proc)
> (display "some text"))
>
> (procedure test-proc)
>
> produces a segfault.
Good catch, thanks! Fixed in git.
Andy
--
http://wingolog.org/
On Sat 30 Oct 2010 17:58, Neil Jerram writes:
> Fabian Schuetz writes:
>
>> (undefine list)
>
> Unless there's a compelling need, I'm afraid it's unlikely anyone will
> work on this, because most developer focus is now on 1.9/2.0.
Indeed, `undefine' doesn't exist in 1.9/2.0.
If you still have
Fabian Schuetz writes:
> While experimenting with "undefine", I discovered, that
> even quite important functions, like "write" or "display"
> can be undefined. The problem is, that calling them
> after they have been "undefined", leads to an
> endless regression, displaying a Segmentation faul
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> Hi Neil,
>
> Neil Jerram <[EMAIL PROTECTED]> writes:
>
>> It would be convenient if it worked though, as then we wouldn't have
>> to invalidate "email bug-guile@gnu.org" as a method of reporting bugs.
>
> Note: just because we recommend using the bug t
Hi Neil,
Neil Jerram <[EMAIL PROTECTED]> writes:
> It would be convenient if it worked though, as then we wouldn't have
> to invalidate "email bug-guile@gnu.org" as a method of reporting bugs.
Note: just because we recommend using the bug tracker doesn't mean we
should ignore messages sent manua
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> Hi,
>
> Neil Jerram <[EMAIL PROTECTED]> writes:
>
>> So would then ask people to raise bugs on savannah, instead of
>> emailing bug-guile? Or can we implement something to catch emails to
>> bug-guile and automatically raise corresponding bugs on sava
Hi,
Neil Jerram <[EMAIL PROTECTED]> writes:
> So would then ask people to raise bugs on savannah, instead of
> emailing bug-guile? Or can we implement something to catch emails to
> bug-guile and automatically raise corresponding bugs on savannah?
> (Surely someone has done that already?)
The f
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>>> (I had forgotten about it, which may be an indication that we should
>>> really start using the bug tracker.)
>>
>> What would that involve?
>
> Not much actually. Just mention it in the relevant pieces of
> documentation. The bug tracker automatic
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> It seems unlikely to introduce a regression. However, that means we
> should keep producing bug-fix releases of 1.6?
I suggest that we ask on the lists if there is any demand for another
1.6.x. When we do this, we should say what has been fixed sinc
Hi,
Neil Jerram <[EMAIL PROTECTED]> writes:
> For 1.6 the fix is slightly different; please see below and let me
> know if you have any comments.
It seems unlikely to introduce a regression. However, that means we
should keep producing bug-fix releases of 1.6?
Thanks,
Ludovic.
_
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> Hi,
>
> Neil Jerram <[EMAIL PROTECTED]> writes:
>
>> I believe the patch below is the correct fix for this. Please test
>> and/or comment!
>
> Works like a charm!
For 1.6 the fix is slightly different; please see below and let me
know if you have any
Hi Neil,
Neil Jerram <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Ludovic Courtès) writes:
>> (I had forgotten about it, which may be an indication that we should
>> really start using the bug tracker.)
>
> What would that involve?
Not much actually. Just mention it in the relevant pieces
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> Hi,
>
> Neil Jerram <[EMAIL PROTECTED]> writes:
>
>> I believe the patch below is the correct fix for this. Please test
>> and/or comment!
>
> Works like a charm!
Thanks for trying it.
>> +2007-10-19 Neil Jerram <[EMAIL PROTECTED]>
>> +
>> +*
Hi,
Neil Jerram <[EMAIL PROTECTED]> writes:
> I believe the patch below is the correct fix for this. Please test
> and/or comment!
Works like a charm!
> +2007-10-19 Neil Jerram <[EMAIL PROTECTED]>
> +
> + * standalone/test-use-srfi: Use -q to avoid picking up the user's
> + ~/.guile
"frank schwidom" <[EMAIL PROTECTED]> writes:
> Original-Nachricht
> Datum: Wed, 10 Oct 2007 18:27:42 +0200
> Von: "frank schwidom" <[EMAIL PROTECTED]>
> An: bug-guile@gnu.org
> Betreff: Segmentation fault
>
> Hi
>
> the following code leads to an segmentation fault in guile-1.6 a
"frank schwidom" <[EMAIL PROTECTED]> writes:
> Original-Nachricht
> Datum: Wed, 10 Oct 2007 18:27:42 +0200
> Von: "frank schwidom" <[EMAIL PROTECTED]>
> An: bug-guile@gnu.org
> Betreff: Segmentation fault
>
> Hi
>
> the following code leads to an segmentation fault in guile-1.6 a
Original-Nachricht
Datum: Wed, 10 Oct 2007 18:27:42 +0200
Von: "frank schwidom" <[EMAIL PROTECTED]>
An: bug-guile@gnu.org
Betreff: Segmentation fault
Hi
the following code leads to an segmentation fault in guile-1.6 and guile-1.8,
when executed with --debug
currently the short
Frithjof <[EMAIL PROTECTED]> writes:
>
> Is my system just not set up correctly or is this a bug in Guile or one in
> the example?
A bug in the example. If you don't have a HOSTNAME variable then
getenv returns NULL, and scm_str2string can't cope with NULL. I'll
change the manual. Thanks.
___
Neil Jerram <[EMAIL PROTECTED]> writes:
> You might like to try making the code for my-hostname safer, like
> this:
We should make the example safe as well...
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
___
Bug-guile mailin
Frithjof <[EMAIL PROTECTED]> writes:
> Hey,
> when trying to compile the example from chapter "2.3.3 Linking
> Guile into Programms" in the Reference Manual with gcc 3.3.5 I get the
> following:
>
> gcc -o simple-guile simple-guile.c -lguile -pthread \
> -Wl,-rpath,/usr/local/lib
>
> (gdb) run
David Hansen <[EMAIL PROTECTED]> writes:
> Hello,
>
> my first guile code started with a SIGSEGV. Not sure if
> it's not my fault but looks like a bug to me.
You need to initialize Guile before using it. For example:
static void
inner_main (void *data, int argc, char **argv)
{
David Hansen <[EMAIL PROTECTED]> writes:
> Hello,
>
> my first guile code started with a SIGSEGV. Not sure if
> it's not my fault but looks like a bug to me.
>
> ,[ gtst.c ]
> | // -*- compile-command: "gcc -g -Wall `guile-config compile` `guile-config link`
> gtst.c -o gtst" -*-
> |
> |
22 matches
Mail list logo
