Vin Shelton writes:
> The new behavior is different, but the problem is not yet fixed.
OK. It's possible that there remain problems in Cygwin, but the
probability of an XEmacs bug is increasing. New backtraces would be
useful, I think, unless Aidan has a guess offhand.
> 4. But when I try t
Andy Koppe writes:
> Meanwhile, Corinna has implemented support for the latter on
> cygwin-cvs, so that mad filename works fine now:
>
> $ touch
> $'ï\202\201Ð\201Ð\201Ð\201ï\203\22002ABFxi-string)g)Àâw\001\200ÑH\001Â\200\t'
> $ ls
> ï??Ð?Ð?Ð?ï??02ABFxi-string)g)Àâw??ÑH?Â??
> $ ls --quot
Andy Koppe writes:
> Hang on, there is a problem with this one: Cygwin doesn't like the
> \001's and the tab at the end.
Well, I'll be damned. I was betting on this being 100% an XEmacs bug,
but I could lose! :-) I'll keep looking for that XEmacs bug, though.
--
Problem reports: http:/
Vin Shelton writes:
> (gdb) pobj charset
> Cannot access memory at address 0x4
Urk. That's unexpected. You might want to try going up the stack to
frame 1 and trying that. If that's not more sensible, what does print
charset say?
Diving into the stack
> #9 0x0056d4d7 in qxe_realpath (pat
Vin Shelton writes:
> XEmacs people - here is the line of code implicated in the crash:
>
>switch (XCHARSET_REP_BYTES (charset))
Can you do a pobj on charset in the debugger and find out what it
actually is?
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Replies directed to xemacs-beta, cygwin/x, and cygwin mailing lists.
I'm not sure that cygwin/x is relevant, but that's what charli
suggested so I'm leaving it in for now.
> "Charli" == Charli Li <[EMAIL PROTECTED]> writes:
>>> From: Yuval Grossman
>>> I am running xemacs (21.4.19) u
6 matches
Mail list logo
