Bookmark and Share

Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

re:RE: Re: AW: st: replace-all can crash do-file


From   Kit Baum <[email protected]>
To   [email protected]
Subject   re:RE: Re: AW: st: replace-all can crash do-file
Date   Sun, 16 May 2010 08:58:44 -0400

<>
Martin said

"(which as Martin indicates is a separate process under Windows)"


Does that mean that I can kill it separately, thus preserving my precious
main process which may hold important data? (Weird that I should ask Kit for
Windows advice, is it not :-) )

In your "Task Manager" or whatever it is called, does the Do-file editor show up as a separate item or process? It does not do so in Unix (incl Linux, Mac OS X) implementations of Stata, where it is part of the Stata process.

I have no idea whether Windows 7 "Ultimate" is able to do what Unix of any flavor was capable of doing ~25 years ago with the "kill -9 pid" superuser command. One would hope that the Microsoft developers would have caught up by now with the notion of processes that do not generally have the capability to stomp on each other's memory space, or take other processes down when they die or hang. Of course, no software is perfect, which is why we get occasional "kernel panics" in Unix systems, sort of like the infamous "blue screen of death" for Windows. I think I had a kernel panic in 2007 on one of my ~5 Unix systems.

Kit Baum   |   Boston College Economics & DIW Berlin   |   http://ideas.repec.org/e/pba1.html
                              An Introduction to Stata Programming  |   http://www.stata-press.com/books/isp.html
   An Introduction to Modern Econometrics Using Stata  |   http://www.stata-press.com/books/imeus.html


*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/


© Copyright 1996–2018 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   Site index