Re: Stack overflow protection/detection

2016-08-31 Thread Johannes Schlatow
Hi Stefan, unfortunately, I cannot reproduce the problem as it was some time ago and I don't remember the exact situation. On Wed, 31 Aug 2016 13:15:44 +0200 Stefan Kalkowski wrote: > Hi Johannes, > > On 08/30/2016 09:40 PM, Johannes Schlatow wrote: > > Norman, thanks a lot for the clarificat

Re: Stack overflow protection/detection

2016-08-31 Thread Stefan Kalkowski
Hi Johannes, On 08/30/2016 09:40 PM, Johannes Schlatow wrote: > Norman, thanks a lot for the clarification! > > I must admit that I only had a rather brief look at the existing code. > > You explanation still leaves me puzzled with one little question though: > Where does the "invalid signal-con

Re: Stack overflow protection/detection

2016-08-30 Thread Johannes Schlatow
Norman, thanks a lot for the clarification! I must admit that I only had a rather brief look at the existing code. You explanation still leaves me puzzled with one little question though: Where does the "invalid signal-context capability" come from? I actually noticed that a couple of times in th

Re: Stack overflow protection/detection

2016-08-30 Thread Norman Feske
Hi Johannes, I'm afraid that you misinterpreted the role of the "stack allocator". Stacks are actually not allocated consecutively but within a sparsely populated area (called stack area) within the component's virtual memory space. We introduced the current stack allocation scheme back in Genode