On 16/08/2013 12:34 AM, Ryan Johnson wrote:
On 15/08/2013 10:35 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
At this point I'm pretty confident it's memory corruption of some kind.
Consider the following semi-STC:
1. Invoke: emacs-nox -Q; echo -e att $(jobs -p)\nc
I'm not subscribed to this list, so if you want me to reply, please CC
me explicitly. Besides, this discussion should be moved to
emacs-de...@gnu.org, since I don't see anything Cygwin specific here
at this point.
Date: Thu, 15 Aug 2013 16:55:18 -0400
From: Ryan Johnson
Again, please move this discussion to emacs-devel.
Date: Thu, 15 Aug 2013 22:35:54 -0400
From: Ken Brown kbr...@cornell.edu
1. Invoke 'emacs-nox -Q' in mintty.
2. M-x compile C-a C-k ls RET
3. C-x o
4. Hit 'g' repeatedly.
I got it to abort with Fatal error 6 after slightly over
Ryan Johnson wrote:
I set a breakpoint there, since I thought it was guaranteed to lead to a
crash if it ever ran, but it turns out that's not true. Invoking M-x
compile triggers the breakpoint twice in a row with the following
(valid!) 5-byte UTF-8:
10XX 10XX 10XX 10XX
Please move this discussion to emacs-de...@gnu.org.
Date: Fri, 16 Aug 2013 01:59:41 -0400
From: Ryan Johnson ryan.john...@cs.utoronto.ca
The variable pending_exact has value 0x0, which would be a Bad Thing...
except that the code looks like this:
if (!pending_exact
On 16/08/2013 5:13 AM, Eli Zaretskii wrote:
Date: Fri, 16 Aug 2013 01:59:41 -0400
From: Ryan Johnson **snip**
Please don't feed the spammers. I get enough as it is...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On 14/08/2013 10:04 AM, Ryan Johnson wrote:
On 10/08/2013 2:01 PM, Ken Brown wrote:
I'm not sure that garbage collection is the underlying problem here.
Agree it's probably not GC... GC would just tend to trip over any bad
pointers that were lurking around...
After a rash of crashes where I
On 8/15/2013 8:32 AM, Ryan Johnson wrote:
On 14/08/2013 10:04 AM, Ryan Johnson wrote:
On 10/08/2013 2:01 PM, Ken Brown wrote:
I'm not sure that garbage collection is the underlying problem here.
Agree it's probably not GC... GC would just tend to trip over any bad
pointers that were lurking
Date: Thu, 15 Aug 2013 12:58:02 -0400
From: Ken Brown kbr...@cornell.edu
CC: Eli Zaretskii e...@gnu.org
Eli is the expert on bidi.c (he wrote it). He can probably tell you
whether you've really bumped into an emacs bug here.
There's nothing wrong with bidi.c here, it just aborts because
On 15/08/2013 1:10 PM, Eli Zaretskii wrote:
Date: Thu, 15 Aug 2013 12:58:02 -0400
From: Ken Brown kbr...@cornell.edu
CC: Eli Zaretskii e...@gnu.org
Eli is the expert on bidi.c (he wrote it). He can probably tell you
whether you've really bumped into an emacs bug here.
There's nothing wrong
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
Program received signal SIGSEGV, Segmentation fault.
___chkstk_ms () at
/usr/src/debug/gcc-4.8.1-1/libgcc/config/i386/cygwin.S:146
You're not using the latest gcc, which is 4.8.1-3. Any chance that
that's your problem?
Ken
--
Problem reports:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
Program received signal SIGSEGV, Segmentation fault.
___chkstk_ms () at
/usr/src/debug/gcc-4.8.1-1/libgcc/config/i386/cygwin.S:146
You're not using the latest gcc, which is 4.8.1-3. Any chance that
that's your
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
Program received signal SIGSEGV, Segmentation fault.
___chkstk_ms () at
/usr/src/debug/gcc-4.8.1-1/libgcc/config/i386/cygwin.S:146
You're not using the latest gcc,
On 8/15/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
Program received signal SIGSEGV, Segmentation fault.
___chkstk_ms () at
/usr/src/debug/gcc-4.8.1-1/libgcc/config/i386/cygwin.S:146
On 15/08/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
Program received signal SIGSEGV, Segmentation fault.
___chkstk_ms () at
On 15/08/2013 6:02 PM, Ken Brown wrote:
On 8/15/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
Program received signal SIGSEGV, Segmentation fault.
___chkstk_ms () at
On 8/15/2013 6:39 PM, Ryan Johnson wrote:
On 15/08/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
Program received signal SIGSEGV, Segmentation fault.
___chkstk_ms () at
On 8/15/2013 6:48 PM, Ryan Johnson wrote:
On 15/08/2013 6:02 PM, Ken Brown wrote:
On 8/15/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
Program received signal SIGSEGV, Segmentation
On 15/08/2013 6:48 PM, Ryan Johnson wrote:
On 15/08/2013 6:02 PM, Ken Brown wrote:
On 8/15/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
Program received signal SIGSEGV, Segmentation
On 8/15/2013 7:14 PM, Ryan Johnson wrote:
On 15/08/2013 6:48 PM, Ryan Johnson wrote:
On 15/08/2013 6:02 PM, Ken Brown wrote:
On 8/15/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
On 15/08/2013 7:07 PM, Ken Brown wrote:
On 8/15/2013 6:48 PM, Ryan Johnson wrote:
On 15/08/2013 6:02 PM, Ken Brown wrote:
On 8/15/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
On 15/08/2013 7:40 PM, Ken Brown wrote:
On 8/15/2013 7:14 PM, Ryan Johnson wrote:
On 15/08/2013 6:48 PM, Ryan Johnson wrote:
On 15/08/2013 6:02 PM, Ken Brown wrote:
On 8/15/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On
On 8/15/2013 8:58 PM, Ryan Johnson wrote:
On 15/08/2013 7:07 PM, Ken Brown wrote:
On 8/15/2013 6:48 PM, Ryan Johnson wrote:
On 15/08/2013 6:02 PM, Ken Brown wrote:
On 8/15/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
At this point I'm pretty confident it's memory corruption of some kind.
Consider the following semi-STC:
1. Invoke: emacs-nox -Q; echo -e att $(jobs -p)\nc /dev/clipboard; fg
2. ^Z
3. (switch to window running gdb and hit [shift]+[insert] to paste from
On 15/08/2013 10:35 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
At this point I'm pretty confident it's memory corruption of some kind.
Consider the following semi-STC:
1. Invoke: emacs-nox -Q; echo -e att $(jobs -p)\nc
/dev/clipboard; fg
2. ^Z
3. (switch to window running
On 10/08/2013 2:01 PM, Ken Brown wrote:
On 8/10/2013 11:24 AM, Ryan Johnson wrote:
On 10/08/2013 9:59 AM, Ken Brown wrote:
On 8/9/2013 11:28 PM, Ryan Johnson wrote:
On 08/08/2013 2:00 PM, Ryan Johnson wrote:
On 08/08/2013 1:42 PM, Ken Brown wrote:
On 8/5/2013 11:29 AM, Ryan Johnson wrote:
On 14/08/2013 10:04 AM, Ryan Johnson wrote:
After a rash of crashes where I either forgot to attach gdb or forgot
to set appropriate breakpoints, I finally managed to catch the stack
trace below. It occurred during M-x compile, while emacs parsed the
compilation's rather copious output, which
#2606 0x0001004dfaf4 in mark_buffer (buffer=optimized out)
at /usr/src/debug/emacs-24.3-4/src/alloc.c:5552
#2607 0x0001004dff2c in Fgarbage_collect ()
at /usr/src/debug/emacs-24.3-4/src/alloc.c:5181
#2608 0x in ?? ()
I don't know whether 2608 stack
On 8/9/2013 11:28 PM, Ryan Johnson wrote:
On 08/08/2013 2:00 PM, Ryan Johnson wrote:
On 08/08/2013 1:42 PM, Ken Brown wrote:
On 8/5/2013 11:29 AM, Ryan Johnson wrote:
On 05/08/2013 11:00 AM, Ken Brown wrote:
On 8/3/2013 3:05 PM, Ryan Johnson wrote:
On 02/08/2013 8:07 AM, Ryan Johnson wrote:
On 10/08/2013 9:59 AM, Ken Brown wrote:
On 8/9/2013 11:28 PM, Ryan Johnson wrote:
On 08/08/2013 2:00 PM, Ryan Johnson wrote:
On 08/08/2013 1:42 PM, Ken Brown wrote:
On 8/5/2013 11:29 AM, Ryan Johnson wrote:
On 05/08/2013 11:00 AM, Ken Brown wrote:
On 8/3/2013 3:05 PM, Ryan Johnson wrote:
On 8/10/2013 11:24 AM, Ryan Johnson wrote:
On 10/08/2013 9:59 AM, Ken Brown wrote:
On 8/9/2013 11:28 PM, Ryan Johnson wrote:
On 08/08/2013 2:00 PM, Ryan Johnson wrote:
On 08/08/2013 1:42 PM, Ken Brown wrote:
On 8/5/2013 11:29 AM, Ryan Johnson wrote:
On 05/08/2013 11:00 AM, Ken Brown wrote:
On 08/08/2013 2:00 PM, Ryan Johnson wrote:
On 08/08/2013 1:42 PM, Ken Brown wrote:
On 8/5/2013 11:29 AM, Ryan Johnson wrote:
On 05/08/2013 11:00 AM, Ken Brown wrote:
On 8/3/2013 3:05 PM, Ryan Johnson wrote:
On 02/08/2013 8:07 AM, Ryan Johnson wrote:
On 02/08/2013 7:04 AM, Ken Brown wrote:
On 8/5/2013 11:29 AM, Ryan Johnson wrote:
On 05/08/2013 11:00 AM, Ken Brown wrote:
On 8/3/2013 3:05 PM, Ryan Johnson wrote:
On 02/08/2013 8:07 AM, Ryan Johnson wrote:
On 02/08/2013 7:04 AM, Ken Brown wrote:
On 8/2/2013 4:02 AM, Corinna Vinschen wrote:
On Aug 1 22:46, Ryan Johnson wrote:
On 08/08/2013 1:42 PM, Ken Brown wrote:
On 8/5/2013 11:29 AM, Ryan Johnson wrote:
On 05/08/2013 11:00 AM, Ken Brown wrote:
On 8/3/2013 3:05 PM, Ryan Johnson wrote:
On 02/08/2013 8:07 AM, Ryan Johnson wrote:
On 02/08/2013 7:04 AM, Ken Brown wrote:
On 8/2/2013 4:02 AM, Corinna Vinschen wrote:
On 8/3/2013 3:05 PM, Ryan Johnson wrote:
On 02/08/2013 8:07 AM, Ryan Johnson wrote:
On 02/08/2013 7:04 AM, Ken Brown wrote:
On 8/2/2013 4:02 AM, Corinna Vinschen wrote:
On Aug 1 22:46, Ryan Johnson wrote:
Here's a new one... I started a compilation, but before it actually
invoked the
On 05/08/2013 11:00 AM, Ken Brown wrote:
On 8/3/2013 3:05 PM, Ryan Johnson wrote:
On 02/08/2013 8:07 AM, Ryan Johnson wrote:
On 02/08/2013 7:04 AM, Ken Brown wrote:
On 8/2/2013 4:02 AM, Corinna Vinschen wrote:
On Aug 1 22:46, Ryan Johnson wrote:
Here's a new one... I started a compilation,
On 02/08/2013 8:07 AM, Ryan Johnson wrote:
On 02/08/2013 7:04 AM, Ken Brown wrote:
On 8/2/2013 4:02 AM, Corinna Vinschen wrote:
On Aug 1 22:46, Ryan Johnson wrote:
Here's a new one... I started a compilation, but before it actually
invoked the command it started pegging the CPU. After
Hi
On Sat, Aug 3, 2013 at 8:05 PM, Ryan Johnson wrote:
Rats. I just had another crash, the Fatal error 6 variety. Windows
Defender has not turned itself back on (it's been known to do that), and a
scan of the BLODA list didn't match anything else on my system.
So I don't think it's BLODA...
On Aug 1 22:46, Ryan Johnson wrote:
On 26/07/2013 11:32 PM, Ryan Johnson wrote:
On 26/07/2013 10:50 PM, Ken Brown wrote:
On 7/26/2013 8:32 PM, Ryan Johnson wrote:
Hi all,
Running 64-bit cygwin 1.7.22(0.268/5/3), with emacs-nox 24.3-4 inside
mintty 1.2-beta1-1, I keep getting seg faults
On 8/2/2013 4:02 AM, Corinna Vinschen wrote:
On Aug 1 22:46, Ryan Johnson wrote:
On 26/07/2013 11:32 PM, Ryan Johnson wrote:
On 26/07/2013 10:50 PM, Ken Brown wrote:
On 7/26/2013 8:32 PM, Ryan Johnson wrote:
Hi all,
Running 64-bit cygwin 1.7.22(0.268/5/3), with emacs-nox 24.3-4 inside
On 02/08/2013 7:04 AM, Ken Brown wrote:
On 8/2/2013 4:02 AM, Corinna Vinschen wrote:
On Aug 1 22:46, Ryan Johnson wrote:
On 26/07/2013 11:32 PM, Ryan Johnson wrote:
On 26/07/2013 10:50 PM, Ken Brown wrote:
On 7/26/2013 8:32 PM, Ryan Johnson wrote:
Hi all,
Running 64-bit cygwin
On 26/07/2013 11:32 PM, Ryan Johnson wrote:
On 26/07/2013 10:50 PM, Ken Brown wrote:
On 7/26/2013 8:32 PM, Ryan Johnson wrote:
Hi all,
Running 64-bit cygwin 1.7.22(0.268/5/3), with emacs-nox 24.3-4 inside
mintty 1.2-beta1-1, I keep getting seg faults and Fatal error 6:
Aborted
It happens
Hi all,
Running 64-bit cygwin 1.7.22(0.268/5/3), with emacs-nox 24.3-4 inside
mintty 1.2-beta1-1, I keep getting seg faults and Fatal error 6: Aborted
The most recent stackdump was:
Stack trace:
FrameFunctionArgs
021F960 0018006F893 (001008C3C40, 4FFF,
On 7/26/2013 8:32 PM, Ryan Johnson wrote:
Hi all,
Running 64-bit cygwin 1.7.22(0.268/5/3), with emacs-nox 24.3-4 inside
mintty 1.2-beta1-1, I keep getting seg faults and Fatal error 6: Aborted
The most recent stackdump was:
Stack trace:
FrameFunctionArgs
021F960 0018006F893
On 26/07/2013 10:50 PM, Ken Brown wrote:
On 7/26/2013 8:32 PM, Ryan Johnson wrote:
Hi all,
Running 64-bit cygwin 1.7.22(0.268/5/3), with emacs-nox 24.3-4 inside
mintty 1.2-beta1-1, I keep getting seg faults and Fatal error 6:
Aborted
It happens at strange times, invariably during I/O of
45 matches
Mail list logo
