[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Invalid output to process
From: |
Richard M. Stallman |
Subject: |
Re: Invalid output to process |
Date: |
Mon, 07 Nov 2005 10:34:32 -0500 |
Why I can't just send you the content of `foo' variable? Because when I
put its value into a buffer and then read it from the buffer, the read
value is equalp to the original `foo' value, but the bug can't be
reproduced with the new value.
I agree that is perplexing, but that is no reason not to show us the
value. The information may be important--and I don't have time to try
to figure out what the value is by reading the code.
Would you please show us the printed form of that value?
I don't understand how this can happen.
Yes, I tried to debug the send_process C function but that
failed on a gdb error:
nevyn/local/gdb/gdb-6.3/gdb/infrun.c:2642: internal-error:
insert_step_resume_breakpoint_at_sal: Assertion `step_resume_breakpoint ==
NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Have you reported a GDB bug?
Meanwhile, what exactly were the GDB commands that you used?
Perhaps there is some other way to "debug the send_process C function"
using different commands that won't encounter this bug.
I suspect that this has something to do with character codings.
I think that your output string is being encoded in some way.
Please try binding coding-system-for-write to `no-conversion'
around the calls to process-send-string and see if that fixes
things.