From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Debugging emacs
Date: Wed, 19 Aug 1998 23:51:42 +0200 [thread overview]
Message-ID: <19980819235142.36595@alpha.franken.de> (raw)
Hi,
before I'll ask a bigger audience, I ask here:
As some of you know, emacs dies, when started to open it's own
X window on Linux/MIPS. While trying to debug emacs with gdb,
I found out, that emacs kills it's own .mdebug section when it dumps
(it inserts a new .data section, which kills all references in
the .mdebug section).
Now I'm looking for a way to start a X session with temacs, which has
a working .mdebug section. I'm able to do a temacs -l loadup, which
will give me a "normal" looking emacs. But I haven't found a way to get
temacs to create a X session.
Any hints ?
Thomas.
--
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
[Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]
next reply other threads:[~1998-08-19 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-19 21:51 Thomas Bogendoerfer [this message]
1998-08-19 22:02 ` Debugging emacs Olivier Galibert
1998-08-20 22:21 ` Thomas Bogendoerfer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19980819235142.36595@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox