gcc --version gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) CNS+tmittelstaedt＠inbuildlnx01:~/bin$ gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7) > -----Ursprüngliche Nachricht----- > Von: Aidan Kehoe [mailto:kehoea＠parhasard.net] > Gesendet: Donnerstag, 5. Juni 2008 13:13 > An: Thomas Mittelstädt > Cc: XEmacs Beta; Jarle Thorsen > Betreff: Re: [Bug: 21.4.21] xemacs segfaults when doing "ls -l" in shell > buffer on 64-bit ubuntu linux 8.04 > > > Ar an cúigiú lá de mí Meitheamh, scríobh Thomas Mittelstädt: > > > Aidan, > > > > I downloaded xemacs 21.4.21 and built it with the same configuration > options as the one that was installed and could not reproduce the crash. > > Strangely, even though I specified --prefix=/usr/local/xemacs-21.4.21, it > would still install into /usr and /usr/lib. > > Good, from my perspective, that probably means it’s not our problem, it’s > GCC’s, or possibly Ubuntu’s :-) . Both you and Jarle have the same compiler, > > gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) > > in your bug reports; what compiler did you use to build from source? That > is, what does gcc --version give? > > > > -----Ursprüngliche Nachricht----- > > > Von: Aidan Kehoe [mailto:kehoea＠parhasard.net] > > > Gesendet: Mittwoch, 4. Juni 2008 17:15 > > > An: Thomas Mittelstädt > > > Cc: XEmacs Beta > > > Betreff: Re: [Bug: 21.4.21] xemacs segfaults when doing "ls -l" in > shell > > > buffer on 64-bit ubuntu linux 8.04 > > > > > > > > > Ar an ceathrú lá de mí Meitheamh, scríobh Thomas Mittelstädt: > > > > > > > Even when I use ls -l --color=never it crashes, but only when my > current > > > directory is $HOME. > > > > > > OK; I suspect you have some non-ASCII or perhaps non-Latin-1 files that > > > provoke that there. Are you in a position where you can provoke this > > > under GDB? I’d be really interested in the specific line number that > > > crashes. > > > > > > Also, beyond that, it’s not surprising that current Mercurial sources > > > don’t crash there, since they leave the string matching to the X11 > > > server in that context. > > > > > > -- > > > ¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir > > > precipitadamente de la aldea por culpa de la escasez de rinocerontes? > > -- > ¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir > precipitadamente de la aldea por culpa de la escasez de rinocerontes?