From: Ivan Andrus <darthandrus@gmail.com>
To: Harald Hanche-Olsen <hanche@math.ntnu.no>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs seems awfully unstable on OS X lately
Date: Fri, 14 Sep 2012 10:37:49 +0200 [thread overview]
Message-ID: <E89532CF-7212-4791-9D71-96D03F93B6F3@gmail.com> (raw)
In-Reply-To: <20120914.092513.1021878789502755268.hanche@math.ntnu.no>
On Sep 14, 2012, at 9:25 AM, Harald Hanche-Olsen wrote:
> Do other OS X users experience stability problems on OS X with recent
> builds from trunk?
Yes. I've been using the Mac Port for the past week or so because of it. I plan to run it under gdb and see if I can track it down, but I haven't had time yet. I'm not sure when I will.
> I built an emacs from current trunk on September 6. It had a tendency
> to get stuck in garbage collection and needing to be killed,
> especially when I tried sending emails with large-ish attachments (on
> the order of a megabyte or two).
>
> So I built a new one yesterday. It is even more unstable, just
> crashing randomly in the main event loop.
I see that here too.
> So for the time being, I have reverted to a version that I build in
> late July, which seems stable enough.
If you can bisect that would probably be helpful.
> I am not sure that I have enough data to send a meaningful bug report.
> Are the OS provided crash logs useful? I have read somewhere that gdb
> doesn't work with the output of the current crop of Apple's compilers,
> so I haven't even tried using that.
I'm on 10.6, but gdb seems to work fine for me.
> I'll try to gather more information on these crashes if needed, but
> then I could use some tips on how to do it. But if others are seeing
> these crashes and are actively working on fixing them, I'll just wait.
I certainly wouldn't wait for me to fix it. :-)
-Ivan
next prev parent reply other threads:[~2012-09-14 8:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 7:25 Emacs seems awfully unstable on OS X lately Harald Hanche-Olsen
2012-09-14 8:37 ` Ivan Andrus [this message]
2012-09-14 15:24 ` Harald Hanche-Olsen
2012-09-14 15:40 ` Óscar Fuentes
2012-09-14 15:59 ` Harald Hanche-Olsen
2012-09-14 19:37 ` Harald Hanche-Olsen
2012-09-14 19:46 ` Harald Hanche-Olsen
2012-09-14 21:15 ` Harald Hanche-Olsen
2012-09-14 21:36 ` Harald Hanche-Olsen
2012-09-14 23:00 ` Óscar Fuentes
2012-09-15 6:54 ` Andreas Schwab
2012-09-15 7:16 ` Eli Zaretskii
2012-09-15 9:37 ` Stephen J. Turnbull
2012-09-15 9:58 ` Eli Zaretskii
2012-09-15 13:46 ` Stephen J. Turnbull
2012-09-15 14:21 ` Eli Zaretskii
2012-09-15 15:00 ` Stephen J. Turnbull
2012-09-15 9:57 ` Harald Hanche-Olsen
2012-09-16 0:47 ` Harald Hanche-Olsen
2012-09-16 8:04 ` Jan Djärv
2012-09-16 13:15 ` Harald Hanche-Olsen
2012-09-16 15:21 ` Jan Djärv
2012-09-16 15:47 ` Harald Hanche-Olsen
2012-09-16 18:27 ` Jan Djärv
2012-09-17 7:14 ` Harald Hanche-Olsen
2012-09-24 9:54 ` Harald Hanche-Olsen
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=E89532CF-7212-4791-9D71-96D03F93B6F3@gmail.com \
--to=darthandrus@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=hanche@math.ntnu.no \
/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).