Re: xemacs crashes with SIGSEGV after update

2015-04-09 Thread Vin Shelton
Siegmar Gross writes: > >> > today I updated all packages of my 32-Bit Cygwin installation >> (installed >> > on top of Windows 7). After that xemacs crashed if I tried to >> open a >> > file. Therefore I reinstalled the older version >> xemacs-21.4.23.1. >> > Unfortunately the old

Re: xemacs crash when fontifying files

2015-02-13 Thread Vin Shelton
"Dr. Volker Zell" writes: >>>>>> Vin Shelton writes: > > > Is this with 21.4.23? There is a patch in 21.4.23 specifically designed > > to work around this. > > Yes.. Oops. I've just applied a patch to 21.4 to fix this.

Re: xemacs crash when fontifying files

2015-02-13 Thread Vin Shelton
Will Parsons writes: > I've recently noticed that xemacs will crash if one attempts to turn on > syntax highlighting via turn-on-font-lock (even started with the -q option), > but only if run under X. (If X is not running, there is no problem.) The > crash causes the following to print: > > Lisp

Re: [ANNOUNCEMENT] Updated: pv-1.3.9-1

2012-12-05 Thread Vin Shelton
indicator of relative throughput > in a complex pipeline This version fails with: zsh: invalid system call pv on a 64-bit W7 install. The previous version (1.3.4.1) worked fine. Please let me know if you need more info. Regards, Vin Shelton -- Problem reports:

Re: New gcc-4 compile error w/getc and isspace

2009-11-09 Thread Vin Shelton
Dave Korn wrote: Vin Shelton wrote: t2.c: In function ‘tst’: t2.c:9: error: lvalue required as left operand of assignment Did something recently change in the ctype.h or stdio.h header files to cause this? Thanks, Dave! - Vin -- Problem reports: http://cygwin.com/problems.html

New gcc-4 compile error w/getc and isspace

2009-11-08 Thread Vin Shelton
Consider this module: #include #include void tst(FILE *fp) { int c; while ( isspace(c = getc(fp)) ) ; return; } gcc-4 -c t2.c t2.c: In function ‘tst’: t2.c:9: error: lvalue required as left operand of assignment I'm pretty sure this module used to compile successfully under gcc-4

Re: Segfault under cygwin 1.7.62

2009-10-12 Thread Vin Shelton
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

Re: Segfault under cygwin 1.7.62

2009-10-08 Thread Vin Shelton
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 &

Re: Segfault under cygwin 1.7.62

2009-10-08 Thread Vin Shelton
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 a

Re: undef WIN32_FILENAMES with cygwin-1.7

2009-06-25 Thread Vin Shelton
Hi, Reini - On Wed, Jun 24, 2009 at 6:43 AM, Reini Urban wrote: > cygwin-1.7 removed support for accepting win32 style pathnames. > xemacs should follow. > > The particular problem was file-truename returning a fabricated windows path, > instead of the POSIX path, which for example failed the mule

Re: under cygwin, zsh cannot run when built against ncurses9-5.7-13

2009-03-14 Thread Vin Shelton
René Berber wrote: Vin Shelton wrote: Charles Wilson wrote: Just for grins, could you rebuild zsh against libncurses9 -- but this time use gcc3? cygiconv-2 and cygncurses-9 use the static gcc-3.4.4 libgcc.a, but you are apparently using the gcc-4.3.2 shared libgcc. I just wonder if that

Re: under cygwin, zsh cannot run when built against ncurses9-5.7-13

2009-03-13 Thread Vin Shelton
Charles Wilson wrote: Vin Shelton wrote: When I build the latest zsh sources on Cygwin 1.7 using ncurses8-5.5.3, I get a working zsh. When I build the same zsh sources against ncurses9-5.7-13, although the build completes successfully, the executable will not run: $ /usr/local/zsh-2009-03-11

under cygwin, zsh cannot run when built against ncurses9-5.7-13

2009-03-13 Thread Vin Shelton
Greetings - When I build the latest zsh sources on Cygwin 1.7 using ncurses8-5.5.3, I get a working zsh. When I build the same zsh sources against ncurses9-5.7-13, although the build completes successfully, the executable will not run: $ /usr/local/zsh-2009-03-11/bin/zsh -f $ echo $? 127 My gue

Re: Upgrade woes ("file in use")

2009-03-12 Thread Vin Shelton
ms when I installed as one user and later tried to run setup as a different user. If memory serves, I got 'file in use' messages. I had to uninstall and reinstall to avoid this. - Vin Shelton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports:

Re: cygwins' emacs does not work in multi-language environment (mule)

2007-07-09 Thread Vin Shelton
erved. Regards, Vin Shelton acs at xemacs dot org -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/

Re: Emacs ignores signals

2007-04-16 Thread Vin Shelton
Christopher Faylor wrote: On Mon, Apr 16, 2007 at 01:48:56PM -0400, Vin Shelton wrote: I've attached it to this message. PLEASE DON'T DO THAT! You've sent a massive attachment to thousands of people, most of whom, are uninterested in said attachment. Please think before

Making a cygwin setup CD

2007-03-19 Thread Vin Shelton
ed by MakeCygwinKit, generates the setup.ini file. These scripts may or may not work for you 'out of the box', but I hope people find these scripts useful or perhaps instructive. Regards, Vin Shelton autorun.inf Description: Binary data MakeCygwinKit Description: Binary data

Re: [ANNOUNCEMENT] Updated: xemacs-21.4.20-2/xemacs-tags-21.4.20-2/xemacs-emacs-common-21.4.20-2

2006-12-16 Thread Vin Shelton
to release a new version with those compatibility links, now? -- Chuck In my opinion, it's probably not worth it, but I would revert the patch if you did add the compatibility link. Regards, Vin Shelton XEmacs Release Manager -- Unsubscribe info: http://cygwin.com/ml/#unsubscr

Re: building a cross compiler for linux

2006-12-12 Thread Vin Shelton
th "-o managed" (see the cygwin doc for "mount"). It's easy to run afoul of either of these two. HTH, Vin Shelton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/

Re: Uhh-oh, I used a non-standard directory for install

2006-11-03 Thread Vin Shelton
es and to handle filenames with spaces. #!/bin/bash cut -f1 -d' ' < /etc/setup/installed.db | grep -v INSTALLED.DB | \ xargs --delim='\n' cygcheck -l | xargs --delim='\n' cygpath -w | \ sed -e 's/\(.*\)/del "\1"/g' | s

Re: gunzip 1.3.5 error reading from stdin on Cygwin

2006-10-29 Thread Vin Shelton
(added cc: to zsh-workers. The original message can be found at http://www.mail-archive.com/cygwin@cygwin.com/msg73620.html ) Vin Shelton wrote: After upgrading my system this morning, I'm getting an error running gunzip when it reads from stdin. Steps to reproduce: wge

gunzip 1.3.5 error reading from stdin

2006-10-24 Thread Vin Shelton
in: invalid compressed data--crc error gunzip: stdin: invalid compressed data--length error Interestingly, gunzip gmp-4.2.1.tar.gz works. I've attached the output of 'cygcheck -s -v -r'. Regards, Vin Shelton Cygwin Configuration Diagnostics Current System

Re: crosstool-0.42 & cygwin

2006-10-03 Thread Vin Shelton
faq, and/or mount the crosstool directory with "-o managed" (see the cygwin doc for "mount"). It's easy to run afoul of either of these two. HTH, Vin Shelton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygw

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

2005-01-07 Thread Vin Shelton
e solved. Point is, this is a > regression -- xemacs-21.4.15 works OK (mind you, I haven't tried > recompiling it with gcc-3.3.3). Henry, AFAIK, we didn't make any changes in 21.4.16 that would account for this. As an experiment, can you try to build 21.4.15 with gcc-3.3.3? I