Re: Program received signal SIGSEGV, Segmentation fault.

[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 messages to the user.
Read the inputs, transform the text, write the output.
ISO-8859-1 or UTF8 or unsimplified Chinese input, doesn't matter.
It only matters that it be NUL byte delimitable, and all encodings
support that.  User messages are not involved here.

> with a broken program.  Period.  Full stop.  Most modern distributions
> use UTF-8 by default, and if you simply write a bare 0xA9 to the
> terminal or output file, that's not going to look right on their
> terminal or editor.

It was a data character, not part of my program.
I am trying to get that character to flow through my program
from my inputs to the output file, but I am having trouble with
the Guile functions that transform the data.  I want to hand the
Guile library a string, a la
   (define my-val (get "val-string"))
where "get" is a function that pulls bytes from the input.
Then, later on,  insert it into the output with:
    (emit my-val)
and have *exactly* what was gotten from the input.
I do not care in the slightest what the current locale is.
I pulled in some arbitrary data with ``(get "val-string")''
and now I want those exact bytes to be emitted where I
have the ``(emit my-val)'' invocation.

> But if that's really what you want, fine, here's how you do it:
> 
>   (fluid-set! %default-port-encoding "ISO-8859-1")
>   (set-port-encoding! (current-output-port) "ISO-8859-1")
>   (set-port-encoding! (current-input-port) "ISO-8859-1")
>   (set-port-encoding! (current-error-port) "ISO-8859-1")
> 
> and make sure to *not* set the locale.

Every time I have a fragment of scheme code, I have a new port.
Doing it this way would require concatenating that text with
the text to invoke.  That adds an allocate, two string copies
and a free to every scheme invocation.  I'll poke around, but
I am guessing there would have to be some more of this set up
for each scheme sequence, yes?
        {
            SCM ln = AG_SCM_INT2SCM(line);
            scm_set_port_filename_x(port, file);
            scm_set_port_line_x(port, ln);
            scm_set_port_column_x(port, SCM_INUM0);
        }