From: Nick Roberts <nickrob@snap.net.nz>
To: filerz-emacs@yahoo.com
Cc: emacs-devel@gnu.org
Subject: Re: GDB debugger mode for Emacs in ELPA
Date: Fri, 27 Jun 2008 17:30:54 +1200 [thread overview]
Message-ID: <18532.31502.712978.906059@kahikatea.snap.net.nz> (raw)
In-Reply-To: <633861.40841.qm@web95012.mail.in2.yahoo.com>
> > > Stack trace follows:
> > >
> > > ntdll.dll!7c901230()
> > > > emacs.exe!w32_abort() Line 8194 C
> > > emacs.exe!r_re_alloc() Line 1030 C
> > >...
> >
> > That looks like a problem with Emacs, not the package. Assuming that you
> > are using GDB, what do you get if you type xbacktrace in the console?
> > (This is a user defined command in .gdbinit which gives a backtrace of
> > Lisp function calls.)
>
> Lisp Backtrace:
> "tar-summarize-buffer" (0x82e794)
> "tar-mode" (0x82e860)
> "progn" (0x82e984)
>...
I can see that the error occurs here (in r_re_alloc in ralloc.c):
if (bloc == NIL_BLOC)
abort ();
I don't know why your stack trace gives no arguments for r_re_alloc as it has
two in ralloc.c. Is it possible that Emacs has found a different copy, i.e.
one without symbols?
Going up one frame:
#if defined USE_MMAP_FOR_BUFFERS
p = mmap_realloc ((POINTER_TYPE **) &b->text->beg, nbytes);
#elif defined REL_ALLOC
p = r_re_alloc ((POINTER_TYPE **) &b->text->beg, nbytes);
#else
p = xrealloc (b->text->beg, nbytes);
Just guessing, but should REL_ALLOC be defined if you built using VS 2003?
(as that seems to imply GNU malloc).
What happened with your MinGW build?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-06-27 5:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 5:52 GDB debugger mode for Emacs in ELPA filerz-emacs
2008-06-27 5:30 ` Nick Roberts [this message]
2008-06-27 9:15 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2008-06-27 5:44 filerz-emacs
2008-06-27 6:09 ` Nick Roberts
2008-06-26 3:45 filerz-emacs
2008-06-26 4:11 ` Nick Roberts
2008-06-26 1:03 Nick Roberts
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=18532.31502.712978.906059@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@gnu.org \
--cc=filerz-emacs@yahoo.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.
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).