[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Debugging low level problems with Valgrind
|
From: |
Eli Zaretskii |
|
Subject: |
Re: Debugging low level problems with Valgrind |
|
Date: |
Thu, 30 Jan 2014 05:45:48 +0200 |
> From: Alex Bennée <address@hidden>
> Cc: address@hidden, address@hidden, address@hidden
> Date: Wed, 29 Jan 2014 20:54:49 +0000
>
> >> From: Alex Bennée <address@hidden>
> >> Date: Wed, 29 Jan 2014 15:44:05 +0000
> >> Cc: Alex Bennée <address@hidden>,
> >> emacs-devel <address@hidden>
> >>
> >> Sadly although I could get temacs to start I couldn't get a working
> >> --daemon process needed to trigger the failure.
> >
> > What prevented you from getting a daemon with temacs? Please report
> > the details.
>
> There isn't much reported by emacs apart from the rather terse:
>
> ...
> Finding pointers to doc strings...
> Finding pointers to doc strings...done
> Pure-hashed: 23631 strings, 3428 vectors, 37030 conses, 3224 bytecodes, 82
> others
> Warning: Cannot convert string
> "-*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
> Error: server did not start correctly
I would suggest a separate bug report about that. This shouldn't
happen.
> How would I start Emacs with a terminal session from which I could
> create X frames? I tried "emacs -nw" but when I execute (new-frame) it
> only brings up a new tty frame.
You should use "emacsclient -c", after starting the server in Emacs.
That is,
temacs -nw
emacsclient -c
should open a GUI frame.