From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: William Bert Newsgroups: gmane.emacs.bugs Subject: bug#14378: Date: Fri, 24 May 2013 15:16:03 -0400 Message-ID: References: <83sj1dsnpg.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=90e6ba6e8a20438a1404dd7ba138 X-Trace: ger.gmane.org 1369423051 31153 80.91.229.3 (24 May 2013 19:17:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 24 May 2013 19:17:31 +0000 (UTC) Cc: 14378@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri May 24 21:17:32 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UfxUY-0000T7-Gv for geb-bug-gnu-emacs@m.gmane.org; Fri, 24 May 2013 21:17:30 +0200 Original-Received: from localhost ([::1]:58184 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfxUX-0004JX-Vq for geb-bug-gnu-emacs@m.gmane.org; Fri, 24 May 2013 15:17:29 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:54453) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfxUO-0004Ic-9x for bug-gnu-emacs@gnu.org; Fri, 24 May 2013 15:17:27 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UfxUH-0006p4-H6 for bug-gnu-emacs@gnu.org; Fri, 24 May 2013 15:17:20 -0400 Original-Received: from [140.186.70.43] (port=44194 helo=debbugs.gnu.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfxUH-0006o8-DS for bug-gnu-emacs@gnu.org; Fri, 24 May 2013 15:17:13 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1UfxV4-0002ly-4K for bug-gnu-emacs@gnu.org; Fri, 24 May 2013 15:18:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: William Bert Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 24 May 2013 19:18:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14378 X-GNU-PR-Package: emacs,ns X-GNU-PR-Keywords: Original-Received: via spool by 14378-submit@debbugs.gnu.org id=B14378.136942302810558 (code B ref 14378); Fri, 24 May 2013 19:18:02 +0000 Original-Received: (at 14378) by debbugs.gnu.org; 24 May 2013 19:17:08 +0000 Original-Received: from localhost ([127.0.0.1]:60783 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1UfxUC-0002kD-8X for submit@debbugs.gnu.org; Fri, 24 May 2013 15:17:08 -0400 Original-Received: from mail-ie0-f180.google.com ([209.85.223.180]:39780) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1UfxU9-0002jY-NG for 14378@debbugs.gnu.org; Fri, 24 May 2013 15:17:06 -0400 Original-Received: by mail-ie0-f180.google.com with SMTP id ar20so13144622iec.39 for <14378@debbugs.gnu.org>; Fri, 24 May 2013 12:16:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dLW2G6hvyx2N1+7UZWL3Yk5YkgWj9/z6ZLpBximf7gM=; b=m4rey7MZ+P0NXD1iulntmEiS1kiS7sz2B+Fli3n8HM9CY+lgIF+eTY6N5oFvD+4fdX WI+4MMSyVd98sfuBEt/OVCT9SOIt1/XSHvANJjR5Tj9BuCsdLl/Rf8hCohMUl+MHzu3T R8U5IT6LfukkKaeH+AsQYTc9IRg7Gy80Thrx7hv+VcIwxP6ANLOvvTXSQwrAIn/p2L/r tVlJCr/MSSJnuQ0bgWh6lh+NSENJUKTAGvE8eyMt9tqqEuFFjpcd5Nuh9gUE2LW6AIdk UO8lRhrHFnTmiXsgt5Qgk6FCviaGYDVVVW9EC2S3rH6V6/imP9PZL+dLhlcRkZb9PJ/l 9+0Q== X-Received: by 10.42.168.198 with SMTP id x6mr13468583icy.45.1369422963112; Fri, 24 May 2013 12:16:03 -0700 (PDT) Original-Received: by 10.64.176.137 with HTTP; Fri, 24 May 2013 12:16:03 -0700 (PDT) In-Reply-To: <83sj1dsnpg.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:74532 Archived-At: --90e6ba6e8a20438a1404dd7ba138 Content-Type: text/plain; charset=ISO-8859-1 I might be misunderstanding your question, but I created the original bug report (at http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14378) via report-emacs-bug, and included a repro from emacs -Q. I dumped an OS X console crash log that may be obscuring the information that report-emacs-bug includes, but it's there toward the bottom of the email. I haven't done a backtrace with gdb before but when I get some time I'll look into it. If I'm misunderstanding or there's more I can do to help, please let me know! I'll include the repro here as well: * Repro from emacs -Q: 0. Obtain magit. I'm using 924a56fe24c3c4acf55daa7266b2e9ad4fc30abb (master HEAD as I write this), but I have also seen this happen with earlier versions for several weeks. 1. (add-to-list 'load-path "/path/to/magit") 2. (require 'magit) 3. Open a file that is in a git repo. For example, I can repro using my own .emacs.d, https://github.com/sandinmyjoints/.emacs.d. It's not very big (184 commits). 4. Do command `magit-status` 5. Hit `l` for magit-log 6. Hit `l` for short log 7. Hit `q` to bury log. 8. Hit `q` to bury magit-status. 9. Repeat steps 4-8 until crash. With my normal .emacs.d, I can repeat it only 2-3 times before crash. With emacs -Q, it takes more like 5-8. Step 6 seems to get a little slower each time it is run. Thanks, William On Thu, May 23, 2013 at 11:47 AM, Eli Zaretskii wrote: > > Date: Thu, 23 May 2013 07:55:56 -0400 > > From: William Bert > > > > This fixes the magit bug: https://github.com/magit/magit/pull/650 > > > > Might be useful in diagnosing / fixing the underlying Emacs bug. > > Is it possible to have a full bug report, done with report-emacs-bug, > and with a recipe to reproduce the problem, and perhaps even a > backtrace from the crash? > > Thanks in advance. > -- williamjohnbert.com | github.com/sandinmyjoints | doread.me | callandresponsedc.org | twitter.com/williamjohnbert --90e6ba6e8a20438a1404dd7ba138 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I might be misunderstanding your question, but I crea= ted the original bug report (at=A0
http://debbugs.gnu.org/cgi/bugreport= .cgi?bug=3D14378) via report-emacs-bug, and included a repro from emacs= -Q. I dumped an OS X console crash log that may be obscuring the informati= on that report-emacs-bug includes, but it's there toward the bottom of = the email.

I haven't done a backtrace with gdb before but when I ge= t some time I'll look into it.

If I'm misu= nderstanding or there's more I can do to help, please let me know!

I'll include the repro here as well:

= 
* Repro from emacs -Q:

0. Obtain magit. I'm using 924a56fe24c3c4acf55daa7266b2e9ad4fc30abb (ma=
ster
HEAD as I write this), but I have also seen this happen with earlier
versions for several weeks.
1. (add-to-list 'load-path "/path/to/magit")
2. (require 'magit)
3. Open a file that is in a git repo. For example, I can repro using my own
.emacs.d, https://github.com/sandinmyjoints/.emac=
s.d. It's not very big
(184 commits).
4. Do command `magit-status`
5. Hit `l` for magit-log
6. Hit `l` for short log
7. Hit `q` to bury log.
8. Hit `q` to bury magit-status.
9. Repeat steps 4-8 until crash.

With my normal .emacs.d, I can repeat it only 2-3 times before crash. With
emacs -Q, it takes more like 5-8. Step 6 seems to get a little slower each
time it is run.

Thanks,
William
=


On Thu, May 23, 2013 at 11:47 AM, Eli Zaretskii <eliz@gnu.org> wr= ote:
> Date: Thu, 23 May 2013 07:55:56 -0400
> From: William Bert <willi= am.bert@gmail.com>
>
> This fixes the magit bug: https://github.com/magit/magit/pull/650
>
> Might be useful in diagnosing / fixing the underlying Emacs bug.

Is it possible to have a full bug report, done with report-emacs-bug,
and with a recipe to reproduce the problem, and perhaps even a
backtrace from the crash?

Thanks in advance.



--
williamjohnbert.com=A0|=A0= github.com/s= andinmyjoints=A0| doread= .me |=A0call= andresponsedc.org=A0|=A0twitter.com/williamjohnbert=A0

--90e6ba6e8a20438a1404dd7ba138--