I noticed in the unix VM if you do a kill -SIGQUIT
then it invokes emergencyDump to print the calling stack and creates a  
image file (perhaps  usable)

I'll consider adding it.

But for now lets see how do you get a dump out.

Ok first find the process ID

ps -ax | grep Squeak

That will print the process id, and the path name.

Then
gdb "/Users/johnmci/Documents/Squeak3.8.0/build/Squeak  
3.8.6Beta5.app/Contents/MacOS/Squeak VM Opt" 12672

At the command prompt issue
break checkForInterrupts
then
c
to continue
which should start Squeak running again and give you
Continuing.
[Switching to process 12672 thread 0x593b]

Breakpoint 1, 0x000c383c in checkForInterrupts ()
then at the comand prompt issue
  call (int) printAllStacks()

and then look at your console.log either via the console application  
found in Applications/Utilities or in
/Library/Logs/Console/userid/console.log

You should find stack traces of all running processes (one hopes).
You can then say
quit
at the command prompt to detach and let the squeak process continue  
running.


Technically checkForInterrupts() routine should be called with a 3 or 4  
ms window. If not when
you first start gdb you can invoke the call (int) printAllStacks()

On Feb 13, 2005, at 11:06 AM, stéphane ducasse wrote:

> Thanks
>
> is it in 3.8 gamma 6548?
> I guess so. This means that it does not solve my problem :(
>
> Stef
>
> On 13 févr. 05, at 17:17, David T. Lewis wrote:
>
>> 6293LowSpaceWatcherFix-dtl
>
>
--
======================================================================== 
===
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
======================================================================== 
===