i'm using 1.3.2. i still wonder though whether i'm not seeing a sscanf bug, as i get a crash on a line with sscanf in it, and my char * pointer is getting corrupted [set to a small number] -- and it occurs on the stack, directly above the last variable that sscanf is supposed to be writing into. here's the code: char *p = line; int cp1, cp2, endcount; int cp1high, cp1low; int dummy; while (*p) /* erase all comments out of the line */ { if (*p == '#') *p = '\0'; else p++; } /* see if line is nothing but whitespace and skip if so */ p = line + strspn (line, " \t\n\r\f"); if (!*p) continue; if ((!ignore_first_column ? <------------------------------------- sscanf (p, "%i %i %n", &cp1, &cp2, &endcount) < 2 : sscanf (p, "%i %i %i %n", &dummy, &cp1, &cp2, &endcount) < 3) || *(line + endcount)) { warn_when_safe (intern ("unicode"), Qnotice, "Unrecognized line in translation file %s:\n%s", XSTRING_DATA (filename), line); continue; } if (cp1 >= st && cp1 <= en) GDB reports the crash on the line indicated, and reports p as 0x24 <address out of bounds>. are you in contact with cygwin people? Charles Wilson wrote:

Ben> how [or whether] it works. Also, pdump might be working; I'm Ben> not sure. It compiles but I haven't had much chance to test Ben> the result. Another thing to note is that coding-system Hi Ben, I get this during building: Here's my -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

Hello! I checked out ben-mule-21-5 and found that my patch for lisp/process.el (Mon, 23 Jul 2001) has not been applied. Has this bug (see below) been fixed in another way? The bug was this: When XEmacs calls a process and feeds a buffer to it it does the following: 1. write the buffer to a file using coding-system-for-write (ok) 2. read this file into another buffer (inbuf) using 'binary (ok) 3. pipe inbuf to the process using coding-system-for-write (BUG!) So the data gets transformed twice by coding-system-for-write. I guess this writing the file and reading it back in will go away in the future, right? Until then, call-process-internal is broken without the patch. -Edwin Here's the patch if you should need it: 2001-07-23 Edwin Steiner <esteiner(a)net4you.at&gt; * process.el (call-process-internal): bind coding-system-for-write to 'binary when calling start-process-internal, so the process receives the literal contents of INFILE. Index: xemacs/lisp/process.el =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/process.el,v retrieving revision 1.9 diff -u -r1.9 process.el --- xemacs/lisp/process.el 2001/06/08 12:21:10 1.9 +++ xemacs/lisp/process.el 2001/07/23 19:13:46 ＠＠ -122,13 +122,17 ＠＠ (when (and stderr (not (eq t stderr))) (setq stderr (expand-file-name stderr)) (setq errbuf (generate-new-buffer "*call-process*"))) - (setq proc - (apply 'start-process-internal "*call-process*" - buffer - ;#### not implemented until my new process - ;changes go in. - ;(if (eq t stderr) buffer (list buffer errbuf)) - program args)) + ;; We read INFILE using the binary coding-system. + ;; We must feed the process using the same coding-system, so + ;; that it really receives the contents of INFILE. + (let ((coding-system-for-write 'binary)) + (setq proc + (apply 'start-process-internal "*call-process*" + buffer + ;#### not implemented until my new process + ;changes go in. + ;(if (eq t stderr) buffer (list buffer errbuf)) + program args))) (if buffer (set-marker (process-mark proc) (point buffer) buffer)) (unwind-protect

"David A. Cobb" wrote: but i don't make use of it one bit. this is plain old sscanf[] that it's crashing in. no widechar/mbchar stuff in parse-unicode-translation-table at all.