BUGREPORT 1.1final - 2 instances of KDevelop

W. Tasin tasin at e-technik.fh-muenchen.de
Mon Feb 28 21:48:10 GMT 2000


"Hummel, Timo" wrote:
> 
> I think the reason is another here. KDevelop creates a file somewhere, and
> if KDevelop crashes, the file remains so that KDevelop notices that it
> wasn't shut down correctly last time. If you run another instance, it
> notices that the file is still there and assumes that KDevelop crashed, but
> it is still running. Another idea would be to use interprocess
> communications or simple a ps and if kdevelop sees itself plus one instance,
> and the file is existant, everything is alright. If there is only one
> instance, it indicates that kdevelop really crashed.
> 

Hi Timo,

very tricky the solution with "one" instance...
hmmm... but how would it work if I have 3 instances running and the
second crashes?
;-)

Ciao

Walter

-- 
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
(Zucchero)
:-------W. Tasin, FB 04,
FHM-------------------PGP-KeyID:0x7961A645----------:
<Key-Fingerprint: 1610 835F 0080 32F4 6140  6CF7 A7D0 44CD 7961A645>
<http://wwwkeys.pgp.net:11371/pks/lookup?op=index&search=0x7961A645&fingerprint=on>




More information about the KDevelop mailing list