On 7/14/2015 6:18 PM, Eric Blake wrote:
In fact, I'm
a bit surprised that emacs rolls its own protection instead of taking
advantage of libsigsegv - it might be worth suggesting that to upstream
emacs.
Good idea. I'll do that.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ
On 06/27/2015 08:52 AM, Corinna Vinschen wrote:
> The problem is probably that there are still resources in use which
> didn't get free'd. I'll check next week if I can do anything about it.
> Ideally with a simple testcase than emacs :}
Is libsigsegv an appropriate testcase? There are several o
Hi Ken,
On Jul 14 15:09, Ken Brown wrote:
> On 7/3/2015 9:09 AM, Ken Brown wrote:
> >I think I found the cause of that second SIGSEGV, and, if I'm right, it
> >has nothing to do with Cygwin. I think the problem was that in my
> >testing, I forgot to reset max-specpdl-size and max-lisp-eval-depth
On 7/3/2015 9:09 AM, Ken Brown wrote:
On 7/3/2015 6:47 AM, Corinna Vinschen wrote:
On Jul 2 15:25, Ken Brown wrote:
On 7/2/2015 8:20 AM, Corinna Vinschen wrote:
On Jul 2 14:13, Corinna Vinschen wrote:
On Jul 1 22:10, Ken Brown wrote:
I may have spoken too soon. As I repeat the experiment
On 7/3/2015 6:47 AM, Corinna Vinschen wrote:
On Jul 2 15:25, Ken Brown wrote:
On 7/2/2015 8:20 AM, Corinna Vinschen wrote:
On Jul 2 14:13, Corinna Vinschen wrote:
On Jul 1 22:10, Ken Brown wrote:
I may have spoken too soon. As I repeat the experiment on a different
computer, with a build
On Jul 3 12:47, Corinna Vinschen wrote:
> In the meantime I found that there's another problem. Assuming you
> longjmp out of handle_sigsegv, the stack will still be "broken".
> It doesn't have the usual guard pages anymore, and the next time
> you have a stack overflow, NTDLL will simply termina
On Jul 2 15:25, Ken Brown wrote:
> On 7/2/2015 8:20 AM, Corinna Vinschen wrote:
> >On Jul 2 14:13, Corinna Vinschen wrote:
> >>On Jul 1 22:10, Ken Brown wrote:
> >>>I may have spoken too soon. As I repeat the experiment on a different
> >>>computer, with a build from a slightly different snapsh
On 7/2/2015 8:20 AM, Corinna Vinschen wrote:
On Jul 2 14:13, Corinna Vinschen wrote:
On Jul 1 22:10, Ken Brown wrote:
I may have spoken too soon. As I repeat the experiment on a different
computer, with a build from a slightly different snapshot of the emacs
trunk, emacs crashes when I type
On Jul 2 14:13, Corinna Vinschen wrote:
> On Jul 1 22:10, Ken Brown wrote:
> > I may have spoken too soon. As I repeat the experiment on a different
> > computer, with a build from a slightly different snapshot of the emacs
> > trunk, emacs crashes when I type 'C-x d' with the following stack du
On Jul 1 22:10, Ken Brown wrote:
> On 7/1/2015 4:12 PM, Ken Brown wrote:
> >On 7/1/2015 9:57 AM, Corinna Vinschen wrote:
> >>On Jul 1 12:47, Corinna Vinschen wrote:
> >>>On Jun 30 16:13, Ken Brown wrote:
> On 6/30/2015 3:55 PM, Corinna Vinschen wrote:
> >On Jun 27 16:52, Corinna Vinschen
On 7/1/2015 4:12 PM, Ken Brown wrote:
On 7/1/2015 9:57 AM, Corinna Vinschen wrote:
On Jul 1 12:47, Corinna Vinschen wrote:
On Jun 30 16:13, Ken Brown wrote:
On 6/30/2015 3:55 PM, Corinna Vinschen wrote:
On Jun 27 16:52, Corinna Vinschen wrote:
On Jun 26 18:28, Ken Brown wrote:
On the other
On 7/1/2015 9:57 AM, Corinna Vinschen wrote:
On Jul 1 12:47, Corinna Vinschen wrote:
On Jun 30 16:13, Ken Brown wrote:
On 6/30/2015 3:55 PM, Corinna Vinschen wrote:
On Jun 27 16:52, Corinna Vinschen wrote:
On Jun 26 18:28, Ken Brown wrote:
On the other hand, emacs doesn't really make a full
On Jul 1 12:47, Corinna Vinschen wrote:
> On Jun 30 16:13, Ken Brown wrote:
> > On 6/30/2015 3:55 PM, Corinna Vinschen wrote:
> > >On Jun 27 16:52, Corinna Vinschen wrote:
> > >>On Jun 26 18:28, Ken Brown wrote:
> > >>>On the other hand, emacs doesn't really make a full recovery. For
> > >>>exam
On Jun 30 16:13, Ken Brown wrote:
> On 6/30/2015 3:55 PM, Corinna Vinschen wrote:
> >On Jun 27 16:52, Corinna Vinschen wrote:
> >>On Jun 26 18:28, Ken Brown wrote:
> >>>On 6/26/2015 4:05 PM, Corinna Vinschen wrote:
> As for getrlimit(RLIMIT_STACK), I changed that as outlined in my former
>
On 6/30/2015 3:55 PM, Corinna Vinschen wrote:
On Jun 27 16:52, Corinna Vinschen wrote:
On Jun 26 18:28, Ken Brown wrote:
On 6/26/2015 4:05 PM, Corinna Vinschen wrote:
As for getrlimit(RLIMIT_STACK), I changed that as outlined in my former
mail in git. On second thought, I also changed the val
On Jun 27 16:52, Corinna Vinschen wrote:
> On Jun 26 18:28, Ken Brown wrote:
> > On 6/26/2015 4:05 PM, Corinna Vinschen wrote:
> > >As for getrlimit(RLIMIT_STACK), I changed that as outlined in my former
> > >mail in git. On second thought, I also changed the values of
> > >MINSIGSTKSZ and SIGSTKS
On Jun 26 18:28, Ken Brown wrote:
> On 6/26/2015 4:05 PM, Corinna Vinschen wrote:
> >As for getrlimit(RLIMIT_STACK), I changed that as outlined in my former
> >mail in git. On second thought, I also changed the values of
> >MINSIGSTKSZ and SIGSTKSZ. Instead of 2K and 8K, they are now defined
> >a
On 6/26/2015 4:05 PM, Corinna Vinschen wrote:
[CC Ben, please keep him on the CC in replies. Thank you]
Hi Ken,
On Jun 26 12:55, Ken Brown wrote:
Hi Corinna,
On 6/26/2015 11:36 AM, Corinna Vinschen wrote:
Thanks. Another question: How does emacs compute stack_bottom?
Very near the beg
[CC Ben, please keep him on the CC in replies. Thank you]
Hi Ken,
On Jun 26 12:55, Ken Brown wrote:
> Hi Corinna,
>
> On 6/26/2015 11:36 AM, Corinna Vinschen wrote:
> >Thanks. Another question: How does emacs compute stack_bottom?
>
> Very near the beginning of main() it does the following
Hi Ken,
On Jun 26 12:55, Ken Brown wrote:
> Hi Corinna,
>
> On 6/26/2015 11:36 AM, Corinna Vinschen wrote:
> >Thanks. Another question: How does emacs compute stack_bottom?
>
> Very near the beginning of main() it does the following:
>
> char stack_bottom_variable;
> [...]
> /* Record (ap
Hi Corinna,
On 6/26/2015 11:36 AM, Corinna Vinschen wrote:
Hi Ken,
On Jun 26 10:33, Ken Brown wrote:
On 6/26/2015 10:14 AM, Corinna Vinschen wrote:
On Jun 26 08:02, Ken Brown wrote:
On 6/26/2015 7:12 AM, Corinna Vinschen wrote:
Thank you. I'll try to test this in the next couple of days.
Hi Ken,
On Jun 26 10:33, Ken Brown wrote:
> On 6/26/2015 10:14 AM, Corinna Vinschen wrote:
> >On Jun 26 08:02, Ken Brown wrote:
> >>On 6/26/2015 7:12 AM, Corinna Vinschen wrote:
> >Thank you. I'll try to test this in the next couple of days. One hint
> >and one question:
> >
> >>The signal handl
Hi Corinna,
On 6/26/2015 10:14 AM, Corinna Vinschen wrote:
Hi Ken,
On Jun 26 08:02, Ken Brown wrote:
On 6/26/2015 7:12 AM, Corinna Vinschen wrote:
On Jun 22 13:08, Corinna Vinschen wrote:
On Jun 21 14:47, Ken Brown wrote:
On 6/20/2015 4:55 PM, Corinna Vinschen wrote:
- First cut of an impl
Hi Ken,
On Jun 26 08:02, Ken Brown wrote:
> On 6/26/2015 7:12 AM, Corinna Vinschen wrote:
> >On Jun 22 13:08, Corinna Vinschen wrote:
> >>On Jun 21 14:47, Ken Brown wrote:
> >>>On 6/20/2015 4:55 PM, Corinna Vinschen wrote:
> - First cut of an implementation to allow signal handlers running on
Hi Corinna,
On 6/26/2015 7:12 AM, Corinna Vinschen wrote:
Hi Ken,
On Jun 22 13:08, Corinna Vinschen wrote:
On Jun 21 14:47, Ken Brown wrote:
On 6/20/2015 4:55 PM, Corinna Vinschen wrote:
- First cut of an implementation to allow signal handlers running on an
alternate signal stack.
- New
Hi Ken,
On Jun 22 13:08, Corinna Vinschen wrote:
> On Jun 21 14:47, Ken Brown wrote:
> > On 6/20/2015 4:55 PM, Corinna Vinschen wrote:
> > >- First cut of an implementation to allow signal handlers running on an
> > > alternate signal stack.
> > >
> > >- New API sigaltstack, plus definitions for
Hi Ken,
On Jun 21 14:47, Ken Brown wrote:
> On 6/20/2015 4:55 PM, Corinna Vinschen wrote:
> >- First cut of an implementation to allow signal handlers running on an
> > alternate signal stack.
> >
> >- New API sigaltstack, plus definitions for SA_ONSTACK, SS_ONSTACK,
> >SS_DISABLE,
> > MINSIG
On 6/20/2015 4:55 PM, Corinna Vinschen wrote:
- First cut of an implementation to allow signal handlers running on an
alternate signal stack.
- New API sigaltstack, plus definitions for SA_ONSTACK, SS_ONSTACK, SS_DISABLE,
MINSIGSTKSZ, SIGSTKSZ.
I must be doing something wrong. Shouldn't
Hi Cygwin friends and users,
I released a TEST version of Cygwin. The version number is 2.1.0-0.1.
This test release is mostly for interested *developers*.
The important news which needs some testing is the implementation of
sigaltstack(2) and the underlying implementation of running a signal
29 matches
Mail list logo
