From: Eli Zaretskii <eliz@gnu.org>
To: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
Cc: 12774@debbugs.gnu.org
Subject: bug#12774: 24.2.50; EMACS 24.2.50.1 crashing
Date: Mon, 05 Nov 2012 19:14:21 +0200 [thread overview]
Message-ID: <83zk2w2cr6.fsf@gnu.org> (raw)
In-Reply-To: <80hap5no5p.fsf@gmail.com>
> From: Vincent Belaïche <vincent.b.1@hotmail.fr>
> Cc: 12774@debbugs.gnu.org
> Date: Sun, 04 Nov 2012 20:50:10 +0100
>
> (gdb) break ralloc.c:352
> Breakpoint 1 at 0x1172ef9: file ralloc.c, line 352.
> (gdb) break w32heap.c:194
> Breakpoint 2 at 0x10a4035: file w32heap.c, line 194.
> (gdb) break w32heap.c:208
> Breakpoint 3 at 0x10a407f: file w32heap.c, line 208.
> (gdb) run
> Starting program: C:\Programme\GNU\Emacs\bin\emacs.exe
> [New Thread 4520.0x11d0]
> [New Thread 4520.0x344]
> [New Thread 4520.0x14b8]
>
> Breakpoint 2, sbrk (increment=-892928) at w32heap.c:200
> (gdb) 200 w32heap.c: No such file or directory.
> continue
> Continuing.
>
> Breakpoint 3, sbrk (increment=-892928) at w32heap.c:211
> 211 in w32heap.c
> (gdb) continue
> Continuing.
As you see, it doesn't stop at the lines where you put the
breakpoints, but on other lines. Don't know what that means; maybe
compiler optimizations, maybe a mismatch between the sources and the
binary.
> (gdb) print excess
> (gdb) No symbol "excess" in current context.
Since you are not in ralloc.c, the variable "excess" indeed is not
known.
> (gdb) print w32_last-error()
> (gdb) No symbol "w32_last" in current context.
That was my bad: I meant w32_last_error().
Anyway, I think I know what to do to avoid these crashes. Thanks.
next prev parent reply other threads:[~2012-11-05 17:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 5:23 bug#12774: 24.2.50; EMACS 24.2.50.1 crashing Vincent Belaïche
2012-11-01 14:57 ` Eli Zaretskii
[not found] ` <DUB102-W598866A2386D9F5F9BE37384600@phx.gbl>
2012-11-01 20:09 ` bug#12774: " Eli Zaretskii
2012-11-01 20:37 ` Vincent Belaïche
2012-11-01 20:40 ` bug#12774: " Eli Zaretskii
2012-11-01 20:47 ` Vincent Belaïche
2012-11-01 21:11 ` bug#12774: " Eli Zaretskii
2012-11-01 21:17 ` Eli Zaretskii
2012-11-03 13:47 ` Vincent Belaïche
2012-11-03 14:16 ` bug#12774: " Eli Zaretskii
2012-11-03 17:20 ` Vincent Belaïche
2012-11-03 17:21 ` Vincent Belaïche
2012-11-03 17:41 ` Vincent Belaïche
2012-11-03 20:07 ` bug#12774: " Eli Zaretskii
[not found] ` <DUB102-W4349F77D26F50F97BC2D7184660@phx.gbl>
2012-11-04 3:46 ` Eli Zaretskii
2012-11-04 16:44 ` Eli Zaretskii
2012-11-01 20:51 ` Vincent Belaïche
2012-11-01 21:00 ` Vincent Belaïche
2012-11-04 8:52 ` bug#12774: RE: bug#12774: 24.2.50; EMACS 24.2.50.1 crashing Vincent Belaïche
2012-11-04 16:22 ` Eli Zaretskii
2012-11-04 19:50 ` Vincent Belaïche
2012-11-05 17:14 ` Eli Zaretskii [this message]
2012-11-07 20:40 ` Vincent Belaïche
2012-11-07 21:14 ` Eli Zaretskii
[not found] <80ehk9nm9p.fsf@gmail.com>
2012-11-05 17:29 ` Eli Zaretskii
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=83zk2w2cr6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12774@debbugs.gnu.org \
--cc=vincent.b.1@hotmail.fr \
/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).