From: Eli Zaretskii <eliz@gnu.org>
To: Christoph Scholtes <cschol2112@googlemail.com>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs 23.4 released
Date: Sun, 29 Jan 2012 21:15:16 +0200 [thread overview]
Message-ID: <83d3a2s4l7.fsf@gnu.org> (raw)
In-Reply-To: <4F259897.1020602@gmail.com>
> Date: Sun, 29 Jan 2012 12:05:59 -0700
> From: Christoph Scholtes <cschol2112@googlemail.com>
> CC: Eli Zaretskii <eliz@gnu.org>, cyd@gnu.org, emacs-devel@gnu.org
>
> On 1/29/2012 11:51 AM, Juanma Barranquero wrote:
> > Could it be related to the omit-frame-pointer problem, if you're using
> > a 4.x gcc? Does it build with optimizations if you use
> > -fno-omit-frame-pointer?
>
> I tried that. Still crashes.
I just tried to build Emacs 23.4, and I'm sorry to say that neither
the optimized build nor the unoptimized one crash for me. They both
build just fine and come up without crashing.
> Backtrace from optimized build with debug symbols:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x010719e8 in lookup_volume_info (root_dir=0x88fcdc "d:\\") at w32.c:2051
> 2051 if (xstrcasecmp (info->root_dir, root_dir) == 0)
What's the problem that causes the crash? Is `info' or
`info->root_dir' a NULL pointer or something?
If nothing else gives a clue, diff Emacs 23.4 sources against 23.3.90,
and then apply the diffs one by one until you get the crash. This
should pinpoint the change which causes this.
next prev parent reply other threads:[~2012-01-29 19:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 17:36 Emacs 23.4 released Chong Yidong
2012-01-28 22:59 ` Stefan Monnier
2012-01-28 23:24 ` Bastien
2012-01-29 17:53 ` Christoph Scholtes
2012-01-29 18:32 ` Eli Zaretskii
2012-01-29 18:41 ` Christoph Scholtes
2012-01-29 18:51 ` Juanma Barranquero
2012-01-29 19:05 ` Christoph Scholtes
2012-01-29 19:15 ` Eli Zaretskii [this message]
2012-01-29 20:35 ` Juanma Barranquero
2012-01-29 21:23 ` Christoph Scholtes
2012-01-29 21:37 ` Juanma Barranquero
2012-01-29 23:50 ` Christoph Scholtes
2012-01-30 0:00 ` Juanma Barranquero
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=83d3a2s4l7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cschol2112@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.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).