public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: emacs won't run
Date: Thu, 05 Dec 2013 14:40:00 -0000	[thread overview]
Message-ID: <52A09047.9040203@gmail.com> (raw)
In-Reply-To: <52A076A5.5050207@netfence.it>

Il 12/5/2013 1:50 PM, Andrea Venturoli ha scritto:
> On 12/04/13 11:56, marco atzeri wrote:
>> Il 12/4/2013 10:20 AM, Andrea Venturoli ha scritto:
>>> Hello.
>>>
>>> Since a bit, emacs won't start under X: no error, no message, nothing.
>>> It just starts and exits after a while without doing anything.
>>>
>>> I can run "emacs -nw" fine.
>>>
>>> How can I diagnose this? Is there any log I can look into? Any utility?
>>>
>>>   bye & Thanks
>>>      av.
>>>
>>
>> use strace.
>
> Thanks.
> Forgive my noobiness, but...
>
>  > strace emacs
>  > strace.exe error creating process emacs, (error 2)
>
> Of course, emacs is a shell script.
>
> So I run "strace emacs-x11": is this ok?

should be.

>
> Running emacs-x11 by itself I get one of two behaviours:
> a) either it hogs the CPU for some seconds, then quits with no effect at
> all;
> b) or it hogs the CPU for a while, then I'll get "Memory exhausted--use
> M-x save-some-buffers then exit and restart Emacs".
>
> I still can't grasp what makes the difference.
>
>
>
> Running it through strace, however, it never exits (still doing nothing
> appreciable); it is also quite hard to kill.
>
>
>
> In the end I got a trace file (which is over 7MB!), but it's nothing I
> can interpret.
> What should I do?
> Anything I should look for?

any seriuos error ;-)

> Any way to make some sense out of this?
> Should I upload it somewhere for someone who might be interested in
> seeing it?

see here
> Problem reports:       http://cygwin.com/problems.html
and follow the "cygcheck -s -v -r > cygcheck.out" point

additonal you can upload the trace file somewhere, so someone could take 
a look


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2013-12-05 14:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04  9:20 Andrea Venturoli
2013-12-04 10:56 ` marco atzeri
2013-12-04 19:21   ` Christopher Faylor
2013-12-05  5:53     ` marco atzeri
2013-12-05 12:50   ` Andrea Venturoli
2013-12-05 14:40     ` marco atzeri [this message]
2013-12-06 13:38       ` Andrea Venturoli
2013-12-06 13:51         ` Max Polk
2013-12-06 14:02           ` Andrea Venturoli
2013-12-06 14:18         ` marco atzeri
2013-12-05 20:10           ` Install Bash 4.2 for Cygwin Javier Murillo Márquez
2013-12-06 15:02             ` Peter Rosin
2013-12-06 15:30               ` Javier Murillo Márquez
2013-12-06 18:20                 ` Peter Rosin
2013-12-06 18:56                   ` Javier Murillo Márquez
2013-12-06 19:18                     ` Christopher Faylor
2013-12-06 14:40           ` emacs won't run Andrea Venturoli
2013-12-06 15:17           ` cgf
2013-12-13 13:34         ` Ken Brown
2013-12-20 18:30           ` Mark Evenson
2013-12-05 15:02     ` Achim Gratz
2013-12-06 13:25       ` Andrea Venturoli
2013-12-06 16:26         ` Ken Brown
2013-12-10  9:34           ` Andrea Venturoli
2013-12-10 11:02             ` Corinna Vinschen
2013-12-04 15:50 ` David Karr
2013-12-05 12:47   ` Andrea Venturoli

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=52A09047.9040203@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).