googling for execve sigkill, it looks like gclcvs might be trying to
map things at the wrong place in its ELF header, where "wrong" means
"not allowed to casual users".
As a user:
$ /lib/ld-linux-x86-64.so.2 --list
/usr/lib/gcl-2.7.0-prof//unixport/saved_ansi_gcl
/usr/lib/gcl-2.7.0-prof//unixport/saved_ansi_gcl: error while loading
shared libraries: /usr/lib/gcl-2.7.0-prof//unixport/saved_ansi_gcl:
failed to map segment from shared object: Permission denied
As root:
# /lib/ld-linux-x86-64.so.2 --list
/usr/lib/gcl-2.7.0-prof//unixport/saved_ansi_gcl
linux-vdso.so.1 => (0x00007fffc59e7000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00007fb3a213d000)
[...]
If I run a gclcvs process and cat its /proc/$pid/maps, I get:
00000000-00812000 r-xp 00000000 fd:00 286779
/usr/lib/gcl-2.7.0-prof/uni
xport/saved_ansi_gcl
00a11000-010a5000 rw-p 00811000 fd:00 286779
/usr/lib/gcl-2.7.0-prof/uni
xport/saved_ansi_gcl
010a5000-031fa000 rwxp 00ea5000 fd:00 286779
/usr/lib/gcl-2.7.0-prof/uni
xport/saved_ansi_gcl
031fa000-0444a000 rw-p 00000000 00:00 0 [heap]
7ffff60bb000-7ffff63a7000 r--p 00000000 fd:00 405172
/usr/lib/locale/locale-arch
ive
[...]
It looks like mapping stuff to page 0 might be disabled by default for
non-root users on my linux kernel (which is the default debian linux
kernel with default configuration).
Can gcl either avoid doing that, or take steps to ensure the
configuration is correct, or at least warn the user and tell him what
configuration settings to change and how?
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
How many big company employees does it take to enact a one-liner change to a
system configuration file? At least one engineer per horizontal layer in the
organization, plus each of their managers, and then some — but in the end
everyone's ass will be covered.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
