On 7/9/2014 8:22 AM, Corinna Vinschen wrote:
On Jul 9 12:15, Corinna Vinschen wrote:
On Jul 8 09:55, Ken Brown wrote:
On 7/7/2014 3:12 PM, Zdzislaw Meglicki wrote:
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 4532.0xa100]
0x7ff974f39e3b in KERNELBASE!Debug
On Jul 9 12:15, Corinna Vinschen wrote:
> On Jul 8 09:55, Ken Brown wrote:
> > On 7/7/2014 3:12 PM, Zdzislaw Meglicki wrote:
> > >Program received signal SIGTRAP, Trace/breakpoint trap.
> > >[Switching to Thread 4532.0xa100]
> > >0x7ff974f39e3b in KERNELBASE!DebugBreak () from
> > >/cygdrive
On Jul 9 12:27, Corinna Vinschen wrote:
> On Jul 8 12:44, Christopher Faylor wrote:
> > On Tue, Jul 08, 2014 at 11:36:07AM -0500, Yaakov Selkowitz wrote:
> > >On 2014-07-08 10:02, Christopher Faylor wrote:
> > >> On Tue, Jul 08, 2014 at 09:55:55AM -0400, Ken Brown wrote:
> > >>> Grasping at straw
On Jul 8 12:44, Christopher Faylor wrote:
> On Tue, Jul 08, 2014 at 11:36:07AM -0500, Yaakov Selkowitz wrote:
> >On 2014-07-08 10:02, Christopher Faylor wrote:
> >> On Tue, Jul 08, 2014 at 09:55:55AM -0400, Ken Brown wrote:
> >>> Grasping at straws, as usual, I wonder if these mysterious crashes c
On Jul 8 09:55, Ken Brown wrote:
> On 7/7/2014 3:12 PM, Zdzislaw Meglicki wrote:
> >Program received signal SIGTRAP, Trace/breakpoint trap.
> >[Switching to Thread 4532.0xa100]
> >0x7ff974f39e3b in KERNELBASE!DebugBreak () from
> >/cygdrive/c/WINDOWS/system32/KERNELBASE.dll
> >(gdb) bt
> >#0
On Tue, Jul 08, 2014 at 11:36:07AM -0500, Yaakov Selkowitz wrote:
>On 2014-07-08 10:02, Christopher Faylor wrote:
>> On Tue, Jul 08, 2014 at 09:55:55AM -0400, Ken Brown wrote:
>>> Grasping at straws, as usual, I wonder if these mysterious crashes could
>>> be related to a bug that Corinna just fixe
On 2014-07-08 10:02, Christopher Faylor wrote:
On Tue, Jul 08, 2014 at 09:55:55AM -0400, Ken Brown wrote:
Grasping at straws, as usual, I wonder if these mysterious crashes could
be related to a bug that Corinna just fixed:
https://cygwin.com/ml/cygwin-cvs/2014-q3/msg4.html
Corinna, is
On Tue, Jul 08, 2014 at 09:55:55AM -0400, Ken Brown wrote:
>On 7/7/2014 3:12 PM, Zdzislaw Meglicki wrote:
>> The current version of Emacs that I have is
>> emacs 24.3.91-1OK
>> emacs debuginfo 24.3.91-1OK
>> emacs-el24.3.91-1
On 7/7/2014 3:12 PM, Zdzislaw Meglicki wrote:
The current version of Emacs that I have is
emacs 24.3.91-1OK
emacs debuginfo 24.3.91-1OK
emacs-el24.3.91-1OK
emacs-w32 24.3.91-1OK
emacs-X11
The current version of Emacs that I have is
emacs 24.3.91-1OK
emacs debuginfo 24.3.91-1OK
emacs-el24.3.91-1 OK
emacs-w32 24.3.91-1OK
emacs-X11 24.3.91-1OK
Cygwin is
Cyg
On 06/17/2014 03:22 PM, Zdzislaw Meglicki wrote:
When I go to snapshots on the Cygwin site, there are
only Cygwin dlls there. Where is the latest Emacs
stuff? And which version of Emacs should go with
which Cygwin dll?
Snapshots are of the Cygwin DLL/package. If you're looking for Emacs, you
g
When I go to snapshots on the Cygwin site, there are
only Cygwin dlls there. Where is the latest Emacs
stuff? And which version of Emacs should go with
which Cygwin dll?
Gustav Meglicki
Indiana University
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygw
Greetings, Ken Brown!
> On 6/17/2014 10:47 AM, Zdzislaw Meglicki wrote:
>> emacs 24.3-7 OK
>> emacs-debuginfo 24.3-7 OK
>> emacs-el 24.3-7
On 6/17/2014 10:47 AM, Zdzislaw Meglicki wrote:
emacs 24.3-7 OK
emacs-debuginfo 24.3-7 OK
emacs-el 24.3-7 OK
emacs-w32
Yes, on running cygcheck -cv gdb I get the same output
as you do: the info documentation is missing. Why is it
missing? Do I need to request it explicitly, or is it
missing from Cygwin distribution?
Gustav Meglicki
Indiana University
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On 17/06/2014 16:47, Zdzislaw Meglicki wrote:
gdb 7.6.50-4
Incomplete
... Is gdb meant to be "Incomplete?" I just ran vanilla
installation, requesting "all."
may be it is just a setup glitch.
Just ask for verbose output
$ cygc
Following my previous message, the versions:
Cygwin DLL version info:
DLL version: 1.7.30
DLL epoch: 19 DLL old termios: 5
DLL malloc env: 28
Cygwin conv: 181
API major: 0
API minor: 272
Shared data: 5
DLL identifier:
OK, the latest crash, after the latest upgrades,
about which in the follow up posting. I was running
emacs-w32 under gdb. Emacs crashed on segmentation
fault and the backtrace points to... (Emacs) alloc.
Here it is:
Program received signal SIGSEGV, Segmentation fault.
0x7ff9778dec8b in ??
On Thu, Jun 5, 2014 at 9:51 PM, Christopher Faylor wrote:
> On Thu, Jun 05, 2014 at 03:05:43PM -0400, Ken Brown wrote:
>>On 6/3/2014 6:00 PM, Zdzislaw Meglicki wrote:
>>> And... another crash. I didn't run it under gdb this
>>> time and it didn't dump anything either, but I got
>>> interesting new
On 6/5/2014 3:51 PM, Christopher Faylor wrote:
On Thu, Jun 05, 2014 at 03:05:43PM -0400, Ken Brown wrote:
On 6/3/2014 6:00 PM, Zdzislaw Meglicki wrote:
And... another crash. I didn't run it under gdb this
time and it didn't dump anything either, but I got
interesting new message I didn't see be
On Thu, Jun 05, 2014 at 03:05:43PM -0400, Ken Brown wrote:
>On 6/3/2014 6:00 PM, Zdzislaw Meglicki wrote:
>> And... another crash. I didn't run it under gdb this
>> time and it didn't dump anything either, but I got
>> interesting new message I didn't see before:
>>
>> *** fatal error - WFSO failed
On 6/3/2014 6:00 PM, Zdzislaw Meglicki wrote:
And... another crash. I didn't run it under gdb this
time and it didn't dump anything either, but I got
interesting new message I didn't see before:
*** fatal error - WFSO failed waiting for timer thread, Win32 error 0
This message comes from the f
This is just to confirm: I had a yet another crash,
was running my emacs session under gdb and captured
the event. The trace is the same as before, that is,
there is a problem in deselect_palette that causes
segmentation fault.
Yes, I will report the bug to Emacs maintainers.
Zdzislaw (Gustav) Me
On 6/3/2014 4:01 PM, Zdzislaw Meglicki wrote:
And another crash... captured under gdb again.
Segmentation fault again, but this time:
Program received signal SIGSEGV, Segmentation fault.
0x000100631d84 in deselect_palette (f=0x0, hdc=0x0) at
/usr/src/debug/emacs-24.3.90-1/src/w32xfns.c:123
And... another crash. I didn't run it under gdb this
time and it didn't dump anything either, but I got
interesting new message I didn't see before:
*** fatal error - WFSO failed waiting for timer thread, Win32 error 0
Interesting? Perhaps all these crashes have something to
do with the timer?
Z
On 06/03/2014 04:01 PM, Zdzislaw Meglicki wrote:
And another crash... captured under gdb again.
Segmentation fault again, but this time:
Program received signal SIGSEGV, Segmentation fault.
0x000100631d84 in deselect_palette (f=0x0, hdc=0x0) at
/usr/src/debug/emacs-24.3.90-1/src/w32xfns.c:1
And another crash... captured under gdb again.
Segmentation fault again, but this time:
Program received signal SIGSEGV, Segmentation fault.
0x000100631d84 in deselect_palette (f=0x0, hdc=0x0) at
/usr/src/debug/emacs-24.3.90-1/src/w32xfns.c:123
123 if (f->output_data.w32->old_palette)
This time we've been running it under gdb and
I managed to capture the crash. It aborted
upon having received SIGABRT, and printed the
following:
Program received signal SIGABRT, Aborted.
0x00010064ed67 in xg_select (fds_lim=4428800, rfds= 0x1800c46cd ,
wfds=0x4392e0, efds=0x439a90, timeout=
On 5/21/2014 4:14 PM, Zdzislaw Meglicki wrote:
It just crashed on me again, after a couple of days
of no crashes at all. The versions of everything
are unchanged since my last message. But this
time, and this is new, I have not seen it before,
it did not give me the gdb option. Instead it just
cr
It just crashed on me again, after a couple of days
of no crashes at all. The versions of everything
are unchanged since my last message. But this
time, and this is new, I have not seen it before,
it did not give me the gdb option. Instead it just
crashed and said: "Segmentation fault (core dumped
On 5/19/2014 10:42 AM, Ken Brown wrote:
On 5/19/2014 9:20 AM, Zdzislaw Meglicki wrote:
(gdb) backtrace
#0 0x7ff9550c9e3b in KERNELBASE!DebugBreak ()
from /cygdrive/c/WINDOWS/system32/KERNELBASE.dll
#1 0x00010061a344 in emacs_abort ()
at /usr/src/debug/emacs-24.3.90-1/src/w32fns.c:8460
On 5/19/2014 9:20 AM, Zdzislaw Meglicki wrote:
I got it this time. It crashed on me just a few seconds after I started it,
while reading mail with rmail. This time I had the right debug info
installed for this version of emacs and here is the backtrace:
==
I got it this time. It crashed on me just a few seconds after I started it,
while reading mail with rmail. This time I had the right debug info
installed for this version of emacs and here is the backtrace:
=
(gdb) backtrace
#0 0x7ff9550c9e3b in KER
On 5/14/2014 5:12 PM, Zdzislaw Meglicki wrote:
OK, I've manage to catch it this time. But it looks like
it didn't get very far, because the info in emacs-w32.exe.dbg
appears to be wrong.
[...]
Reading symbols from /usr/bin/emacs-w32.exe...
warning: the debug information found in "/usr/lib/debug//
OK, I've manage to catch it this time. But it looks like
it didn't get very far, because the info in emacs-w32.exe.dbg
appears to be wrong. Here's what happens:
515 $ ps -ef
UID PIDPPID TTYSTIME COMMAND
gustav 19900 1 ?07:51:01 /usr/bin/ssh-agent
gustav 38280 17
35 matches
Mail list logo
