[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gforth] [bug #26261] Seeing assembly code on Mac OS X robs me of my

From: Anton Ertl
Subject: [Bug-gforth] [bug #26261] Seeing assembly code on Mac OS X robs me of my identity
Date: Tue, 21 Apr 2009 17:07:18 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20080702 Iceape/1.1.11 (Debian-1.1.11-1)

Update of bug #26261 (project gforth):

                  Status:                    None => Works For Me           
             Assigned to:                    None => paysan                 


Follow-up Comment #1:

Bernd Paysan has tried this on MacOS X 10.5.6, and could not reproduce
the problem.  Maybe you can follow the suggestions I made in my mail,
and find out more information about the issue, which we can then use
somewhere in the installation.

To have this stuff in the bug tracker and in case my mail has not
reached you, here I reproduce my text:

That means you are using DISASM-GDB for SEEing primitives.  This word
invokes a number of shell commands (in particular: type mktemp echo
gdb rm); my guess is that one of these commands (at least as invoked
by Gforth) has the side effect you observe.

Since you still have the same uid (and are in the same groups), you
should still have the same permissions, and tools should be able to
look up your user name in /etc/passwd (if they look there) in the
traditional Unix security model.  I guess what you are seeing is an
effect of some additional security framework, but I am not familiar
with that (whatever it is), so I cannot really help you there.

The following are just educated guesses: I have read about SELinux
that someone needs to finetune the policies for the various
applications. By default they are restrictive, and if you notice that
it is forbidding something that's ok, you should allow that.  My guess
is that gdb's use of ptrace() to attach to the gforth process looks
suspicious to your security framework and it then disallows some
things.  Maybe you find something about this in the logs of your
security framework.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]