hi, Whenever I use gdb as mortal user, I get the following error: stroessl@mantrasun1:~/<3>Gamik/bin>gdb Hippo GNU gdb 4.18 [snip] This GDB was configured as "sparc-sun-solaris2.7"... (gdb) b main Breakpoint 1 at 0x24e38: file main.c, line 44. (gdb) r Starting program: /home/stroessl/PhD/Hippo/Private/Gamik/bin/Hippo /proc/26876: Value too large for defined data type. PIOCSTATUS or PIOCWSTOP failed. (gdb) This happens with all programs to be debugged. as root, it works fine. I tried to get gdb5-0 to work as mortal user, but I get: stroessl@mantrasun1:~/<3>Gamik/bin>~/gdb-5.0/bin/gdb Hippo GNU gdb 5.0 [snip] This GDB was configured as "sparc-sun-solaris2.7"... (gdb) b main Breakpoint 1 at 0x24e38: file main.c, line 44. (gdb) r Starting program: /home/stroessl/PhD/Hippo/Private/Gamik/bin/Hippo procfs:4036 -- process not stopped. procfs: ...giving up... (gdb) my system config: stroessl@mantrasun1:~/<3>Gamik/bin>uname -a SunOS mantrasun1 5.7 Generic_106541-10 sun4u sparc SUNW,Ultra-1 stroessl@mantrasun1:~/<3>Gamik/bin>showrev Hostname: mantrasun1 Hostid: 80886e80 Release: 5.7 Kernel architecture: sun4u Application architecture: sparc Hardware provider: Sun_Microsystems Domain: sidi.epfl.ch Kernel version: SunOS 5.7 Generic 106541-10 January 2000 I'm not sure if that is related to the noexec_user_stack variable problem of some solaris patches. I don't get segmentation faults, but I don't even reach the very first line of the program... how can I work around this without having to migrate to dbx? tom -- --------------------------------------- Thomas Stroesslin
