When a unix vm crashes, it dumps a crash log to stderr or stdout. When a windows vm crashes, it appends a crash log to vmpath/crash.dmp Where does the mac vm hide such niceties? -- Matthew Fulmer (a.k.a. Tapple) |
On 16 March 2011 02:14, Matthew Fulmer <[hidden email]> wrote: > > When a unix vm crashes, it dumps a crash log to stderr or > stdout. > > When a windows vm crashes, it appends a crash log to > vmpath/crash.dmp > > Where does the mac vm hide such niceties? > Eliot shown me where Cog hiding it.. but i already forgot that :) It is somewhere in your home dir ~/Library .. > -- > Matthew Fulmer (a.k.a. Tapple) > -- Best regards, Igor Stasenko AKA sig. |
In reply to this post by Tapple Gao
On 16.03.2011, at 02:14, Matthew Fulmer wrote: > > When a unix vm crashes, it dumps a crash log to stderr or > stdout. > > When a windows vm crashes, it appends a crash log to > vmpath/crash.dmp > > Where does the mac vm hide such niceties? Newer OS X versions store debug output in a database rather than text files. Apple provides the "Console" app to browse it, including crash reports. Run it, select "all messages", and type "squeak" (or whatever the name of your VM is) in the filter box to see only messages pertaining to Squeak. This is where stderr goes to, so you see e.g. the printStacks output there. In the same app, click "User Diagnostic Reports" to see stored crash reports. The context menu will let you reveal them in Finder. - Bert - |
On 16.03.2011, at 15:57, Bert Freudenberg wrote: > > > On 16.03.2011, at 02:14, Matthew Fulmer wrote: > >> >> When a unix vm crashes, it dumps a crash log to stderr or >> stdout. >> >> When a windows vm crashes, it appends a crash log to >> vmpath/crash.dmp >> >> Where does the mac vm hide such niceties? > > Newer OS X versions store debug output in a database rather than text files. > > Apple provides the "Console" app to browse it, including crash reports. > > Run it, select "all messages", and type "squeak" (or whatever the name of your VM is) in the filter box to see only messages pertaining to Squeak. This is where stderr goes to, so you see e.g. the printStacks output there. > > In the same app, click "User Diagnostic Reports" to see stored crash reports. The context menu will let you reveal them in Finder. > > - Bert - Oh, and the command line equivalent would be syslog -C | grep -i squeak - Bert - |
In reply to this post by Igor Stasenko
On Wed, Mar 16, 2011 at 4:57 AM, Igor Stasenko <[hidden email]> wrote:
~/Library/Logs/DiagnosticReports is where 10.5 and later store it ~/Library/Logs/CrashReporter is IIRC where 10.4 and previous stores it
e.g. Library/Logs/DiagnosticReports/Teleplace_2011-03-11-121210_McStalker.crash
|
In reply to this post by Tapple Gao
The Mac vm uses the same code as the unix vm to trap the signal , then to dump the squeak stack. If the squeak oops space is corrupt you can have that code fail too. Otherwise You should see lot's of messages in the syslog On 3/15/11, Matthew Fulmer <[hidden email]> wrote: > > When a unix vm crashes, it dumps a crash log to stderr or > stdout. > > When a windows vm crashes, it appends a crash log to > vmpath/crash.dmp > > Where does the mac vm hide such niceties? > > -- > Matthew Fulmer (a.k.a. Tapple) > -- =========================================================================== John M. McIntosh <[hidden email]> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com =========================================================================== |
Free forum by Nabble | Edit this page |