On Oct 13 05:20, Stephen J. Turnbull wrote:
> 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,
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
Vin Shelton wrote:
> Do I need some additional cygwin changes other than the dll?
It's worth a try; there have been recent changes to the system headers.
Install the entire "-inst" package from the snapshot, then rebuild xemacs.
--
Chuck
--
Problem reports: http://cygwin.com/problems.h
On Mon, Oct 12, 2009 at 6:46 AM, Stephen J. Turnbull wrote:
> 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
2009/10/12 Aidan Kehoe:
> > and how does it change unexpectedly in terms of POSIX/Cygwin operations?
> > And, importantly, what's the locale setting?
>
> We’re testing our handling of the file name encoding; we want to make sure
> we can create a file with this name when we force the file name en
Ar an naoiú lá de mí Deireadh Fómhair, scríobh Andy Koppe:
> What change exactly? What's the original filename here,
> and how does it change unexpectedly in terms of POSIX/Cygwin operations?
> And, importantly, what's the locale setting?
We’re testing our handling of the file name
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
2009/10/9 Stephen J. Turnbull:
> > 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 don't think you've got anything to worry about there. ;)
[Send again to include the XEmacs list]
On Oct 9 07:05, Andy Koppe wrote:
> \001's and the tab at the end.
>
> $ touch $'\001' $'\t'
> touch: cannot touch `\001': No such file or directory
> touch: cannot touch `\t': No such file or directory
>
> In fact it appears that no control chars are allo
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:/
On Oct 9 07:05, Andy Koppe wrote:
> \001's and the tab at the end.
>
> $ touch $'\001' $'\t'
> touch: cannot touch `\001': No such file or directory
> touch: cannot touch `\t': No such file or directory
>
> In fact it appears that no control chars are allowed in filenames.
Indeed, and it's even
2009/10/9 Vin Shelton:
>> > #3 0x005151bc in Lstream_really_write (lstr=0x176ea00,
>> > data=0x148d0c0
>> >
>> "c;C:\\cygwin\\cygwin\\tmp\\s360339.aoa\\ï\202\201Ð\201Ð\201Ð\201ï\203\22002ABFxi-string)g)Àâw\001\200ÑH\001Â\200\t",
Hang on, there is a problem with this one: Cygwin doesn't li
2009/10/9 Vin Shelton:
>> > #9 0x0056d4d7 in qxe_realpath (path=0x22248c "",
>> > resolved_path=0x22651c
>> > "c:/cygwin/tmp/s360339.aoa/\201Ð\201Ð\201Ð\201Ð02ABFx",
>> > links_only=0) at
>> > #8 0x0056cd68 in readlink_or_correct_case (name=,
>> > buf=0x21e464
>> >
>> "/tmp/s
Stephen -
Thanks again for taking this up.
On Thu, Oct 8, 2009 at 2:36 PM, Stephen J. Turnbull wrote:
> 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
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
On Thu, Oct 8, 2009 at 5:13 AM, Stephen J. Turnbull wrote:
> 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
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:
17 matches
Mail list logo
