Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-17 Thread Bruce Korb
Hi Noah, Mark, On 11/16/12 18:19, Noah Lavine wrote: > OK, so I tried latin1, too. (replacing scm_from_utf3_string with > scm_from_latin1_string). That also does not work. It replaced the > 0xA9 character with '?'. > > > I am no expert on character encodings, but we've seen errors

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-17 Thread Mark H Weaver
Bruce Korb writes: > On 11/16/12 20:22, Mark H Weaver wrote: >> Bruce, if you refuse to fix these problems properly, you will end up > > Hi Mark, > > My program's intent is to read text from two inputs and weave them > together. It has no need to know or understand the encoding in any way, To we

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-17 Thread Bruce Korb
On 11/16/12 20:22, Mark H Weaver wrote: > Bruce, if you refuse to fix these problems properly, you will end up Hi Mark, My program's intent is to read text from two inputs and weave them together. It has no need to know or understand the encoding in any way, other than to communicate exception m

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-16 Thread Mark H Weaver
Bruce Korb writes: > On 11/16/12 13:23, Mark H Weaver wrote: >>> Actually, it was scm_from_utf8_string, since GUILE_VERSION was 25 >> >> Okay, that's the problem. You told Guile that the C string was encoded >> in UTF-8, but actually it was encoded in Latin-1: > > OK, so I tried latin1, too.

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-16 Thread Noah Lavine
Hello, On Fri, Nov 16, 2012 at 6:32 PM, Bruce Korb wrote: > On 11/16/12 13:23, Mark H Weaver wrote: > >> Actually, it was scm_from_utf8_string, since GUILE_VERSION was 25 > > > > Okay, that's the problem. You told Guile that the C string was encoded > > in UTF-8, but actually it was encoded

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-16 Thread Bruce Korb
On 11/16/12 13:23, Mark H Weaver wrote: >> Actually, it was scm_from_utf8_string, since GUILE_VERSION was 25 > > Okay, that's the problem. You told Guile that the C string was encoded > in UTF-8, but actually it was encoded in Latin-1: OK, so I tried latin1, too. (replacing scm_from_utf3_st

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-16 Thread Mark H Weaver
Bruce Korb writes: >>> figure out what caused the SIGSEGV. I don't even know what function you >> >> scm_from_locale_string(). I had a stack trace that disappeared >> from the email. (Typo of some sort. Sorry.) > > Actually, it was scm_from_utf8_string, since GUILE_VERSION was 25 Okay, t

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-16 Thread Bruce Korb
> "AG_SCM_STR02SCM()" is a Guile-version dependent macro: > > $ fgrep GUILE_VERSION ../config.h > #define GUILE_VERSION 25 > > an edited extract from my version dependent wrapper header: > > #elif GUILE_VERSION < 20 > # define AG_SCM_STR02SCM(_s) scm_from_locale_string(_s) >

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-16 Thread Bruce Korb
On 11/16/12 11:19, Mark H Weaver wrote: > Hi Bruce, > > Bruce Korb writes: >> This is a clumsy way of saying you don't like the '©' character in >> strings. > > I'm sorry, but you haven't provided nearly enough information for me to I'm sorry, I did leave off the backtrace. Here's another GDB

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-16 Thread Mark H Weaver
Hi Bruce, Bruce Korb writes: > This is a clumsy way of saying you don't like the '©' character in > strings. I'm sorry, but you haven't provided nearly enough information for me to figure out what caused the SIGSEGV. I don't even know what function you called, or what arguments you passed to it