I do not yet have a machine that I can use to look at or use your code, but
when a library function appears to stuff up I would look for somewhere that
you are overstepping some array bound especially if you malloc the array
space.
Phill
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Robert
> Graham Merkel
> Sent: Wednesday, September 20, 2000 8:27 PM
> To: Dave Peticolas
> Cc: Robert Graham Merkel; [EMAIL PROTECTED]
> Subject: Re: Another bug
[snip]
> > Is there any error message on the core dump? Before we enlarged
> > the stack size, guile would print a very specific error message
> > if we exceeded the stack size.
>
> No, nothing like that. I've traced the crash with gdb, and it happens
> in g-wrap generated code calling a C string->scm type
> conversion function with what appears to be a legitimate C
> string. Odd.
>
> ------------------------------------------------------------
> Robert Merkel [EMAIL PROTECTED]
>
> ------------------------------------------------------------
>
> _______________________________________________
> gnucash-devel mailing list
> [EMAIL PROTECTED]
> http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
>
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
