GNU bug report logs -
#13140
24.3.50; emacs_backtrace.txt
Previous Next
Reported by: "Drew Adams" <drew.adams <at> oracle.com>
Date: Tue, 11 Dec 2012 15:51:02 UTC
Severity: normal
Tags: moreinfo
Merged with 13150,
13153
Found in version 24.3.50
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
>>> In case this is somehow due to a defect in the build I made [1], it
>>> would be good that someone made and upload a build of the current
>>> trunk, so that Drew could try it and see if the crashes happen then
>>> too.
>>
>> Drew, if you're interested you can grab a build from today's trunk at
>> https://www.dropbox.com/sh/3pgcb3iiy8s9irl/c171Xhsd99
>
> Juanma, did you configure with "--enable-checking" ?
>
> I ask this because I configured with it, and IIUC, these backtraces
> that Drew is getting are due to assertions which are enabled only if
> Emacs was configured with that option.
>
> OTOH, I also passed "--no-opt" to the configure script, which perhaps
> might make a difference too.
Answering myself: yes, you used both of those options:
In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
of 2012-12-13 on ODIEONE
Bzr revision: 111211 eggert <at> cs.ucla.edu-20121213021749-eyqqen0ewhn2hogq
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --cflags
-IC:/Devel/emacs/build/include -Wall -Wextra -Wno-sign-compare
-Wno-type-limits -Wno-missing-field-initializers -Wno-pointer-sign
-Wdeclaration-after-statement --ldflags -LC:/Devel/emacs/build/lib'
So, if Drew doesn't get this backtrace again, I guess that the problem
is in my build (unless it was an error in code, fixed between your bzr
revision and mine). But I don't know what I'm doing wrong...
--
Dani Moncayo
This bug report was last modified 11 years and 108 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.