If you can't see what's going on inside the headless image, getting some 
sort of picture would be a start. Try doing this in the image and save it:

[
     [
         f _ FileDirectory default fileNamed: 'allMyProcesses'.
         f nextPutAll: Time now asString; cr.
         Process allInstances do: [ :p |
             p suspendedContext ifNotNilDo: [ :ctxt | f nextPutAll: 
'priority: ',p priority asString; cr;
                 nextPutAll: ctxt longStack; cr; cr]
         ].
         f close.
         (Delay forSeconds: 30) wait
     ] repeat
] forkAt: 60

the output might point you to where things stand.

On 2/7/13 12:14 PM, Jeff Gonis wrote:
>
> Hi everyone,
>
> I am currently working on getting the Squeak Jenkins server to perform 
> benchmarking and so far everything is going great except for one 
> thing. When I try to filein code implementing some benchmarks into a 
> headless VM, it just hangs. If I filein the same file to a 
> non-headless VM everything works just fine.
>
> Seeing as how things only blow up when I am running headless, 
> debugging is made somewhat more complicated.
>
> I was wondering if anyone had some advice on getting better debug 
> information from a headless VM, besides explicit log statements? I was 
> also wondering if this sort of problem is ringing any bells for anyone 
> on the list. I don't really have a good grip on how filein works 
> either, so any pointers would be greatly appreciated. Would filein be 
> attempting to send ui messages that are failing? I didn't see any user 
> input requests when I filed into a normal VM, so I don't think it is 
> waiting on a response. Any help is appreciated.
>
> Thanks for your time,
> Jeff
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20130207/57531fc1/attachment.htm