* bug#13140: 24.3.50; emacs_backtrace.txt
@ 2012-12-11 15:49 Drew Adams
2012-12-11 15:59 ` Eli Zaretskii
0 siblings, 1 reply; 16+ messages in thread
From: Drew Adams @ 2012-12-11 15:49 UTC (permalink / raw)
To: 13140
Backtrace:
0x01154B7D
0x01154BEF
0x01001459
0x0102190E
0x0114A734
0x7E418730
0x7E418812
0x7E4189C9
0x7E418A0C
0x01148D5C
0x01148FFB
0x7C80B725
BTW, ever since the introduction of the emacs_backtrace.txt files, when I get a
crash now I get TWO fatal-error dialog boxes, not one. One is on top of the
other (staggered slightly), and interacting with the top one (I click No)
removes both of them and ends Emacs (closes all frames).
In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
of 2012-12-07 on MS-W7-DANI
Bzr revision: 111150 eggert@cs.ucla.edu-20121207175317-wxhrqxpp0173whq0
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --cflags
-Ic:/emacs/libs/libXpm-3.5.10/include -Ic:/emacs/libs/libXpm-3.5.10/src
-Ic:/emacs/libs/libpng-1.2.37-lib/include -Ic:/emacs/libs/zlib-1.2.5
-Ic:/emacs/libs/giflib-4.1.4-1-lib/include
-Ic:/emacs/libs/jpeg-6b-4-lib/include
-Ic:/emacs/libs/tiff-3.8.2-1-lib/include
-Ic:/emacs/libs/libxml2-2.7.8-w32-bin/include/libxml2
-Ic:/emacs/libs/gnutls-3.0.9-w32-bin/include
-Ic:/emacs/libs/libiconv-1.9.2-1-lib/include'
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-11 15:49 bug#13140: 24.3.50; emacs_backtrace.txt Drew Adams
@ 2012-12-11 15:59 ` Eli Zaretskii
2012-12-12 3:10 ` Drew Adams
0 siblings, 1 reply; 16+ messages in thread
From: Eli Zaretskii @ 2012-12-11 15:59 UTC (permalink / raw)
To: Drew Adams; +Cc: 13140
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Tue, 11 Dec 2012 07:49:33 -0800
>
> BTW, ever since the introduction of the emacs_backtrace.txt files, when I get a
> crash now I get TWO fatal-error dialog boxes, not one. One is on top of the
> other (staggered slightly), and interacting with the top one (I click No)
> removes both of them and ends Emacs (closes all frames).
This means Emacs gets a second fatal error while processing the first
one.
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-11 15:59 ` Eli Zaretskii
@ 2012-12-12 3:10 ` Drew Adams
2012-12-12 3:56 ` Drew Adams
2012-12-12 3:58 ` Eli Zaretskii
0 siblings, 2 replies; 16+ messages in thread
From: Drew Adams @ 2012-12-12 3:10 UTC (permalink / raw)
To: 'Eli Zaretskii'; +Cc: 13140
> > BTW, ever since the introduction of the emacs_backtrace.txt
> > files, when I get a crash now I get TWO fatal-error dialog
> > boxes, not one. One is on top of the other (staggered
> > slightly), and interacting with the top one (I click No)
> > removes both of them and ends Emacs (closes all frames).
>
> This means Emacs gets a second fatal error while processing
> the first one.
OK, well it seems to happen systematically - ever since the introduction of
emacs_backtrace.txt. Dunno if others are seeing this, but IIRC I've seen it
each time Emacs created a backtrace file.
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-12 3:10 ` Drew Adams
@ 2012-12-12 3:56 ` Drew Adams
2013-02-23 1:08 ` Glenn Morris
2012-12-12 3:58 ` Eli Zaretskii
1 sibling, 1 reply; 16+ messages in thread
From: Drew Adams @ 2012-12-12 3:56 UTC (permalink / raw)
To: 'Eli Zaretskii'; +Cc: 13140
I didn't pay attention that the backtraces I got today were in fact identical.
Sorry about that. (I keep getting them.)
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-12 3:10 ` Drew Adams
2012-12-12 3:56 ` Drew Adams
@ 2012-12-12 3:58 ` Eli Zaretskii
2012-12-12 7:31 ` Dani Moncayo
1 sibling, 1 reply; 16+ messages in thread
From: Eli Zaretskii @ 2012-12-12 3:58 UTC (permalink / raw)
To: Drew Adams; +Cc: 13140
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <13140@debbugs.gnu.org>
> Date: Tue, 11 Dec 2012 19:10:04 -0800
>
> > > BTW, ever since the introduction of the emacs_backtrace.txt
> > > files, when I get a crash now I get TWO fatal-error dialog
> > > boxes, not one. One is on top of the other (staggered
> > > slightly), and interacting with the top one (I click No)
> > > removes both of them and ends Emacs (closes all frames).
> >
> > This means Emacs gets a second fatal error while processing
> > the first one.
>
> OK, well it seems to happen systematically - ever since the introduction of
> emacs_backtrace.txt. Dunno if others are seeing this, but IIRC I've seen it
> each time Emacs created a backtrace file.
It never happened to me.
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-12 3:58 ` Eli Zaretskii
@ 2012-12-12 7:31 ` Dani Moncayo
2012-12-12 8:14 ` Glenn Morris
2012-12-12 18:11 ` Juanma Barranquero
0 siblings, 2 replies; 16+ messages in thread
From: Dani Moncayo @ 2012-12-12 7:31 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 13140
>> > > BTW, ever since the introduction of the emacs_backtrace.txt
>> > > files, when I get a crash now I get TWO fatal-error dialog
>> > > boxes, not one. One is on top of the other (staggered
>> > > slightly), and interacting with the top one (I click No)
>> > > removes both of them and ends Emacs (closes all frames).
>> >
>> > This means Emacs gets a second fatal error while processing
>> > the first one.
>>
>> OK, well it seems to happen systematically - ever since the introduction of
>> emacs_backtrace.txt. Dunno if others are seeing this, but IIRC I've seen it
>> each time Emacs created a backtrace file.
>
> It never happened to me.
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.
--------------
[1] Although the last one was made with a clean bootstrap, but who knows.
--
Dani Moncayo
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-12 7:31 ` Dani Moncayo
@ 2012-12-12 8:14 ` Glenn Morris
2012-12-12 15:20 ` Juanma Barranquero
2012-12-12 16:18 ` Drew Adams
2012-12-12 18:11 ` Juanma Barranquero
1 sibling, 2 replies; 16+ messages in thread
From: Glenn Morris @ 2012-12-12 8:14 UTC (permalink / raw)
To: Dani Moncayo; +Cc: 13140
Dani Moncayo wrote:
> 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.
Why do some people on MS Windows find it impossible to build Emacs for
themselves?
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-12 8:14 ` Glenn Morris
@ 2012-12-12 15:20 ` Juanma Barranquero
2012-12-12 16:18 ` Drew Adams
1 sibling, 0 replies; 16+ messages in thread
From: Juanma Barranquero @ 2012-12-12 15:20 UTC (permalink / raw)
To: Glenn Morris; +Cc: 13140
On Wed, Dec 12, 2012 at 9:14 AM, Glenn Morris <rgm@gnu.org> wrote:
> Why do some people on MS Windows find it impossible to build Emacs for
> themselves?
Not impossible, but Windows users do not have a package manager to
ease downloading all the required tools (compiler and build
environment, plus image libraries, some unix-style tools, etc.). If
the user does not really need all these except to compile Emacs, it's
understandable that some or many of them will chose to avoid the
hassle and rely on prepackaged binaries.
Juanma
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-12 8:14 ` Glenn Morris
2012-12-12 15:20 ` Juanma Barranquero
@ 2012-12-12 16:18 ` Drew Adams
1 sibling, 0 replies; 16+ messages in thread
From: Drew Adams @ 2012-12-12 16:18 UTC (permalink / raw)
To: 'Glenn Morris', 'Dani Moncayo'; +Cc: 13140
> > 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.
>
> Why do some people on MS Windows find it impossible to build Emacs for
> themselves?
How could anyone answer wrt your hypothetical "some people"? And are you
perhaps presuming that anyone who does not build Emacs "finds it impossible" to
do so?
What is your real problem about this? And how is it related to fixing the bug
reported in this thread?
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-12 7:31 ` Dani Moncayo
2012-12-12 8:14 ` Glenn Morris
@ 2012-12-12 18:11 ` Juanma Barranquero
2012-12-12 18:14 ` Drew Adams
2012-12-13 19:53 ` Dani Moncayo
1 sibling, 2 replies; 16+ messages in thread
From: Juanma Barranquero @ 2012-12-12 18:11 UTC (permalink / raw)
To: Drew Adams; +Cc: 13140
On Wed, Dec 12, 2012 at 8:31 AM, Dani Moncayo <dmoncayo@gmail.com> wrote:
> 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
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-12 18:11 ` Juanma Barranquero
@ 2012-12-12 18:14 ` Drew Adams
2012-12-13 19:53 ` Dani Moncayo
1 sibling, 0 replies; 16+ messages in thread
From: Drew Adams @ 2012-12-12 18:14 UTC (permalink / raw)
To: 'Juanma Barranquero'; +Cc: 13140
> Drew, if you're interested you can grab a build from today's trunk at
> https://www.dropbox.com/sh/3pgcb3iiy8s9irl/c171Xhsd99
Thanks, Juanma. I'll pick it up tonight after work.
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-12 18:11 ` Juanma Barranquero
2012-12-12 18:14 ` Drew Adams
@ 2012-12-13 19:53 ` Dani Moncayo
2012-12-13 20:04 ` Dani Moncayo
2012-12-14 10:24 ` martin rudalics
1 sibling, 2 replies; 16+ messages in thread
From: Dani Moncayo @ 2012-12-13 19:53 UTC (permalink / raw)
To: Juanma Barranquero; +Cc: 13140
>> 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.
--
Dani Moncayo
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-13 19:53 ` Dani Moncayo
@ 2012-12-13 20:04 ` Dani Moncayo
2014-02-10 4:47 ` Lars Ingebrigtsen
2012-12-14 10:24 ` martin rudalics
1 sibling, 1 reply; 16+ messages in thread
From: Dani Moncayo @ 2012-12-13 20:04 UTC (permalink / raw)
To: Juanma Barranquero; +Cc: 13140
>>> 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@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
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-13 19:53 ` Dani Moncayo
2012-12-13 20:04 ` Dani Moncayo
@ 2012-12-14 10:24 ` martin rudalics
1 sibling, 0 replies; 16+ messages in thread
From: martin rudalics @ 2012-12-14 10:24 UTC (permalink / raw)
To: Dani Moncayo; +Cc: Juanma Barranquero, 13140
> 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.
Practically all backtraces Drew sent come from broken assertions.
martin
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-12 3:56 ` Drew Adams
@ 2013-02-23 1:08 ` Glenn Morris
0 siblings, 0 replies; 16+ messages in thread
From: Glenn Morris @ 2013-02-23 1:08 UTC (permalink / raw)
To: 13140
AFAICS, nobody ever decoded this backtrace; so nothing can be done.
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#13140: 24.3.50; emacs_backtrace.txt
2012-12-13 20:04 ` Dani Moncayo
@ 2014-02-10 4:47 ` Lars Ingebrigtsen
0 siblings, 0 replies; 16+ messages in thread
From: Lars Ingebrigtsen @ 2014-02-10 4:47 UTC (permalink / raw)
To: Dani Moncayo; +Cc: Juanma Barranquero, 13140
Dani Moncayo <dmoncayo@gmail.com> writes:
> 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@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...
This was a year ago, so I'm closing this bug because it's thought that
it might be a build issue. Please reopen if still present.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2014-02-10 4:47 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-11 15:49 bug#13140: 24.3.50; emacs_backtrace.txt Drew Adams
2012-12-11 15:59 ` Eli Zaretskii
2012-12-12 3:10 ` Drew Adams
2012-12-12 3:56 ` Drew Adams
2013-02-23 1:08 ` Glenn Morris
2012-12-12 3:58 ` Eli Zaretskii
2012-12-12 7:31 ` Dani Moncayo
2012-12-12 8:14 ` Glenn Morris
2012-12-12 15:20 ` Juanma Barranquero
2012-12-12 16:18 ` Drew Adams
2012-12-12 18:11 ` Juanma Barranquero
2012-12-12 18:14 ` Drew Adams
2012-12-13 19:53 ` Dani Moncayo
2012-12-13 20:04 ` Dani Moncayo
2014-02-10 4:47 ` Lars Ingebrigtsen
2012-12-14 10:24 ` martin rudalics
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).