Some months ago, I asked about the status of GDB5 on 64-bit Solaris host/target combinations. I interpreted the reply as "it works, doesn't it?" It seems not to, but the behavior I get is such an immediate show-stopper that it makes me believe that the problem must be extremely sensitive to configuration (i.e., I have the wrong one and my respondants don't). I have also found archived mail from people experiencing the same difficulty that I do. A recent (20 Jan 2001) version of GDB 5 sources configured on an UltraSparc (sun4u sparc SUNW,Ultra-5_10) running Solaris 2.7 with .../configure sparc64-sun-solaris2.7 compiled using GCC 2.8.1 when run on an executable compiled with cc -xarch=v9 -g -o test64 test64.c displays the following anomalies: b main Cannot access memory at address 0x0 <<<<???? (gdb) b test64.c:8 Breakpoint 1 at 0xc: file test64.c, line 8. (gdb) run Starting program: /export/home/users/hilfingr/gdb/test64 procfs:3887 -- process not stopped. <<<< ????? procfs: ...giving up... Any assistance or comments gratefully received. Paul Hilfinger _______________________________________________ Bug-gdb mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gdb