mime_db entry pointing to non-existing file prevents replicant from working

[pulkomandy]

I had an entry in mime_db pointing to a non-existing file.

This was picked up when trying to locate the executable for a replicant, and the actual executable was not found.

Moreover, the error message from the zombie replicant only shows the "short description" from that file, making the issue a bit difficult to debug.

It would be nice in this situation if we would:

• Show the path to the executable that was tried (in my case it wasn't even an executable, it was an rsrc file) instead or in addition to the short description
• Try harder, if the MIME db didn't work, to look for the executable that is trying to instanciate the replicant
• On initial instanciation, maybe the message could include a node_ref to the original executable, to make sure the right thing is instanciated?

[bipolar]

On initial instanciation, maybe the message could include a node_ref to the original executable, to make sure the right thing is instanciated?

That sounds like it could help/solve the case of testing custom builds of OS provided replicants. Am I too off?

I'm thinking in the case of AboutSystem, for example, where to test my changes, I had to blacklist app/AboutSystem at boot time (lesson learnt the hard way :-D).