1. Strange Solaris (2.5) defunct process.
I a have a problem with my process becoming defunct at exit.
Basically the process does the following:
Get the _physical_ memory address of a buffer
(physically contigous memory from a dma device driver).
Open /dev/mem and map this address to my address space.
Write the data to _raw_ disk device. (/dev/rdsk/xxx, scsi disk)
Close all, and unmap.
I do not start any processes/threads or async io from my program.
The process reaches the exit call, but the parent process does not
seem to get SIGCHLD, and my process becomes defunct.
The problem only happens with the setup above. If I change my program
to write to a normal file or non raw disk device (/dev/dsk/xxx),
or if I allocate some memory and copy the data from the mapped
area to this memory and write the _copy_ to any file/device,
the problem dissappears. I.e. the problem seems to only occur with
the combination mapped /dev/mem and /dev/rdsk/xxx.
(The /dev/mem mapping will not exists in the final program,
the device driver should be able to do this.)
Has anyone _any_ idea of what this could be?
I do not think I am overwriting any memory/stack (like the parent pid),
making the exit call fail, as my (test) program is quite simple.
Could this be a bug in the rdsk driver?
Staale L. Hansen | Spacetec A.S, Prestvannv. 38,
Software Engineer | N-9005 Tromsoe, Norway
WWW: http://www.spacetec.no | Fax: +47 77 65 58 59
2. what file executes at logout?
3. Solaris 2.5 has runaway/defunct processess?
4. Mklinux on a PB Duo 2300c?
5. FS: Solaris 2.5 Desktop (CDE) and/or Solaris 2.5 Server Packages for x86 desktops
7. corruption of process shared text with Solaris 2.5 on 670MP?
8. solaris 7 network connection pb
9. Defunct Process on Solaris!!!!
10. looping processes under solaris 2.5
11. Why <defunct> process after leaving a fork()ed process?
12. defunct processes on Solaris 1.0
13. Patch for defunct processes under Solaris 2.4?