However, while I now get over the initial assertion failure, I run instead into procfs: couldn't find pid 0 in procinfo list. procfs: init_inferior, open_proc_files line 2878, /proc/6031: No such file or directory. When I break in procfs.c (procfs_init_inferior), I can see that create_procinfo succeeds. However, looking at the process tree at this point, I see that the debuggee is still marked as defunct 18377 /vol/gcc/bin/gdb -i=mi /vol/gnu/obj/gdb/gdb/reghunt/no-r 18379 /vol/gnu/obj/gdb/gdb/reghunt/no-resync/122457/gdb/gdb 18382 so open_procinfo_files fails because /proc/ only contains psinfo and usage, but no ctl file yet. I tried to do the same with a version of gdb from immediately before the multi-target merge: while that can run a test program interactively just fine, running that gdb under gdb itself most often leads to the same error. This very much seems like a race condition to me, but at the moment I'm pretty much at a loss how to investigate this further. So I'd very much appreciate any suggestions and help to make gdb work again on Solaris. Thanks. Rainer -- ----------------------------------------------------------------------------- Rainer Orth, Center for Biotechnology, Bielefeld University