Launchpad has imported 12 comments from the remote bug at
https://bugzilla.novell.com/show_bug.cgi?id=439086.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-10-26T22:55:31+00:00 Galtgendo wrote:

This has came up when I was looking at the biuld system mono uses.
I'm not sure I classified this bug correctly.

The problem is:
in revision 69955, mono/mini/mdb-debug-info64.s did receive a fix to
prevent that executable from getting an executable stack,
but my question is: what was the reason mono/mini/mdb-debug-info32.s
didn't receive same fix ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/0

------------------------------------------------------------------------
On 2008-10-26T23:29:52+00:00 Vargaz wrote:

-> runtime.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/1

------------------------------------------------------------------------
On 2009-03-22T20:42:51+00:00 Galtgendo wrote:

Well, after five months, I'd be happy to receive any answer,
even "your question is stupid", as long as it explains, why is it
stupid.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/2

------------------------------------------------------------------------
On 2009-03-22T21:11:31+00:00 Vargaz wrote:

I have no idea.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/3

------------------------------------------------------------------------
On 2009-03-22T22:44:47+00:00 Galtgendo wrote:

Well, somebody did create that revision, so
perhaps that person can shed some light on this issue ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/4

------------------------------------------------------------------------
On 2009-04-02T06:55:28+00:00 Leszek 'skolima' Ciesielski wrote:

That change has been made by Martin Baulig, so I'm adding him as CC.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/5

------------------------------------------------------------------------
On 2009-04-02T15:25:07+00:00 Ub71a-martin-b69y0 wrote:

Setting to RESOLVED / INVALID since this is not a bug but a question
....

Rafal, if I remember correctly this is only on x86_64 because the on-
executable stack needs hardware and kernel support which exists on the
AMD64, but not necessarily on i386.

I'm not entirely sure since it's been a very long time since I wrote
that code, but I think the reason for making the stack non-executable
was because that is the default in mono when running on x86_64, but not
on i386.

Martin

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/6

------------------------------------------------------------------------
On 2009-04-02T16:13:50+00:00 Galtgendo wrote:

(In reply to comment #6)
> Setting to RESOLVED / INVALID since this is not a bug but a question ....
> 
> Rafal, if I remember correctly this is only on x86_64 because the 
> on-executable
> stack needs hardware and kernel support which exists on the AMD64, but not
> necessarily on i386.
> 
> I'm not entirely sure since it's been a very long time since I wrote that 
> code,
> but I think the reason for making the stack non-executable was because that is
> the default in mono when running on x86_64, but not on i386.
> 
> Martin

Well, that's definitely an answer to a question, just not to mine.

Mine was: during build of mono on x86, libraries/executables
are created by gnu linker, which contain executable stack;
the sole source of it is mono/mini/mdb-debug-info32.s;
does mono need this file to create executable stack in
those libraries/executables ?

Note, that I did try to add that note for non-executable
in that file and mono built fine and it did compile a trivial
program, I'm simply not sure, if I did broke anything that way.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/7

------------------------------------------------------------------------
On 2009-04-02T16:18:11+00:00 Galtgendo wrote:

Or more exactly: on amd64 executable stack is not needed,
is it different on x86 ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/8

------------------------------------------------------------------------
On 2009-08-03T17:32:50+00:00 Kees Cook wrote:

Ironically, the mono/mini/mdb-debug-info64.s file doesn't need the
markings at all.  the mono/mini/mdb-debug-info32.s is the one that needs
the markings (since only ia32 defaults to executable stack when asm
lacks the flags).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/9

------------------------------------------------------------------------
On 2009-08-03T19:00:15+00:00 Ub71a-martin-b69y0 wrote:

Since we're not going to touch this code anyways, -> RESOLVED / INVALID
again.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/12

------------------------------------------------------------------------
On 2011-11-09T23:57:39+00:00 Dan Wallis wrote:

Still appears to be a problem in v2.10.5

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/comments/16


** Changed in: mono (openSUSE)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/408499

Title:
  mono has an executable stack on 32bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/408499/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to