From: E Sabof <esabof@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16741@debbugs.gnu.org, Dmitry Antipov <dmantipov@yandex.ru>
Subject: bug#16741: Crash while using org-mode, narrowing, and vc-git
Date: Sat, 26 Dec 2015 13:41:21 +0000 [thread overview]
Message-ID: <CAEp6DyYCH3AbBWyZzAK0yY4wNSNaapnv-AkFY+Ct4w0demqXGQ@mail.gmail.com> (raw)
In-Reply-To: <87oadd2v3k.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
Basically I didn't manage to reproduce it with valgrind.
On Sat, Dec 26, 2015 at 1:33 PM, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Dmitry Antipov <dmantipov@yandex.ru> writes:
>
> > On 02/13/2014 03:33 PM, E Sabof wrote:
> >
> >> Program received signal SIGABRT, Aborted.
> >> 0x00007fd4ac8f0f77 in __GI_raise (sig=sig@entry=6)
> >> at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> >> 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> >> (gdb) backtrace
> >> #0 0x00007fd4ac8f0f77 in __GI_raise (sig=sig@entry=6)
> >> at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> >> #1 0x00007fd4ac8f45e8 in __GI_abort () at abort.c:90
> >> #2 0x00007fd4ac938aca in __malloc_assert (
> >> assertion=assertion@entry=0x7fd4aca426e0 "(unsigned long)(size)
> >= (unsigned long)(nb)", file=file@entry=0x7fd4aca3e18d "malloc.c",
> >> line=line@entry=3637,
> >> function=function@entry=0x7fd4aca3e48b <__func__.11428>
> "_int_malloc")
> >> at malloc.c:288
> >> #3 0x00007fd4ac93c324 in _int_malloc (av=0x7fd4acc7b740 <main_arena>,
> >> bytes=<optimized out>) at malloc.c:3637
> >> #4 0x00007fd4ac93d4d0 in __GI___libc_malloc (bytes=1008) at
> malloc.c:2859
> >
> > Obviously this is a heap corruption. Please try to 1) provide a recipe to
> > reproduce and 2) run temacs under 'valgrind --tool=memcheck' (slow!) to
> catch
> > memory errors (also use --log-file=log.txt since an output may be huge).
>
> More information was requested, but no response was given within a few
> months, so I'm closing this bug report. If the problem still exists,
> please reopen this bug report.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
[-- Attachment #2: Type: text/html, Size: 2531 bytes --]
prev parent reply other threads:[~2015-12-26 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 11:33 bug#16741: Crash while using org-mode, narrowing, and vc-git E Sabof
2014-02-13 11:50 ` Dmitry Antipov
2015-12-26 13:33 ` Lars Ingebrigtsen
2015-12-26 13:41 ` E Sabof [this message]
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=CAEp6DyYCH3AbBWyZzAK0yY4wNSNaapnv-AkFY+Ct4w0demqXGQ@mail.gmail.com \
--to=esabof@gmail.com \
--cc=16741@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=larsi@gnus.org \
/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).