From: Manoj Srivastava <srivasta@ieee.org>
To: emacs-devel@gnu.org
Subject: Current CVS versions kills Xserver
Date: Tue, 03 Jun 2008 22:20:11 -0500 [thread overview]
Message-ID: <87ej7d9990.fsf@anzu.internal.golden-gryphon.com> (raw)
Hi,
My last couple of compiles tend to kill off my X server (which
makes it a real pain to Debug). I tried it under XNest, and it killed
that too.
I think I'll stay away for a few days, and see if this issue
persists.
manoj
__> startx -- /usr/bin/Xnest :10 -geometry 1280x1024 ~/var/spool/mail
FreeType: couldn't open face /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/Junicode-Italic.ttf: 1
FreeType: couldn't open face /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/Junicode-Italic.ttf: 1
*** glibc detected *** /usr/bin/Xnest: malloc(): memory corruption: 0x0000000001c88fa0 ***
======= Backtrace: =========
/lib/libc.so.6[0x7f4b69fb8fad]
/lib/libc.so.6[0x7f4b69fbb236]
/lib/libc.so.6[0x7f4b69fbc1f6]
/lib/libc.so.6(realloc+0x127)[0x7f4b69fbcda7]
/usr/bin/Xnest(Xrealloc+0x1b)[0x6a59eb]
/usr/bin/Xnest[0x45a8a7]
/usr/bin/Xnest[0x45adcd]
/usr/bin/Xnest[0x423e55]
/usr/bin/Xnest[0x422225]
/usr/bin/Xnest[0x65ef23]
/usr/bin/Xnest[0x443a90]
/usr/bin/Xnest[0x433bbc]
/usr/bin/Xnest[0x435400]
/usr/bin/Xnest[0x447b4d]
/lib/libc.so.6(__libc_start_main+0xf4)[0x7f4b69f681c4]
/usr/bin/Xnest[0x41fc19]
======= Memory map: ========
00400000-0075e000 r-xp 00000000 fd:00 2213382 /usr/bin/Xnest
0095e000-00981000 rw-p 0035e000 fd:00 2213382 /usr/bin/Xnest
00981000-009b7000 rw-p 00981000 00:00 0
0149f000-01f34000 rw-p 0149f000 00:00 0 [heap]
7f4b64000000-7f4b64021000 rw-p 7f4b64000000 00:00 0
7f4b64021000-7f4b68000000 ---p 7f4b64021000 00:00 0
7f4b68466000-7f4b6847c000 r-xp 00000000 08:12 1887850 /lib/libgcc_s.so.1
7f4b6847c000-7f4b6867c000 ---p 00016000 08:12 1887850 /lib/libgcc_s.so.1
7f4b6867c000-7f4b6867d000 rw-p 00016000 08:12 1887850 /lib/libgcc_s.so.1
7f4b686a1000-7f4b686bc000 rw-s 00000000 00:09 1632763931 /SYSV00000000 (deleted)
7f4b686bc000-7f4b686d7000 r--s 00000000 00:09 1353383953 /SYSV00000000 (deleted)
7f4b686d7000-7f4b68723000 r--p 00000000 fd:00 7127469 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf
7f4b68723000-7f4b688a4000 rw-p 7f4b68723000 00:00 0
7f4b688a4000-7f4b68965000 rw-s 00000000 00:09 1632731162 /SYSV00000000 (deleted)
7f4b68965000-7f4b68a26000 r--s 00000000 00:09 1265991694 /SYSV00000000 (deleted)
7f4b68a26000-7f4b68bc4000 rw-p 7f4b68a26000 00:00 0
--
In Corning, Iowa, it's a misdemeanor for a man to ask his wife to ride
in any motor vehicle.
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
next reply other threads:[~2008-06-04 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 3:20 Manoj Srivastava [this message]
2008-06-04 13:38 ` Current CVS versions kills Xserver Manoj Srivastava
2008-06-04 17:18 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ej7d9990.fsf@anzu.internal.golden-gryphon.com \
--to=srivasta@ieee.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).