Really strange.  My changes were almost entirely refactorings.  I
can't think of any reason they should cause a segfault.

What's the input file being fed to this image (as the first arg after
the image name)?  Whatever it's doing, it appears to be loading
something from some MC repository, which triggers a call to
ClassBuilder>recompile:from:to:mutate: which causes the
updateInstancesFrom: on CanvasCharacterScanner.

Which package and version is it trying to load when it crashes?  That
might offer a clue..



On Tue, Oct 15, 2013 at 4:05 PM, Frank Shearar <frank.shearar at gmail.com> wrote:
> On 15 October 2013 21:30, Frank Shearar <frank.shearar at gmail.com> wrote:
>> On 15 October 2013 19:45,  <commits at source.squeak.org> wrote:
>>> Chris Muller uploaded a new version of System to project The Trunk:
>>> http://source.squeak.org/trunk/System-cmm.602.mcz
>>>
>>> ==================== Summary ====================
>>>
>>> Name: System-cmm.602
>>> Author: cmm
>>> Time: 15 October 2013, 1:45:33.881 pm
>>> UUID: 7a452144-3c88-4726-9692-a6afa93ef46e
>>> Ancestors: System-eem.601
>>>
>>> - Support Preferences class>>#readDocumentAtStartup: false, so that Squeak can accept arbitrary arguments without requiring the first one to be a document URL.
>>> - Convenience method for checking for any of the various headless VM  options.
>>> - API consistency for accessing command-line arguments.
>>> - Remove duplicate code (#extractParameters).  Bid to remove apparently-unused code.
>>> - RecentMessages simplifications, fixes and cleanups.
>>>
>>> =============== Diff against System-eem.601 ===============
>>
>> This might be temporal, or temperamental, coincidence but
>> http://build.squeak.org/job/SqueakTrunk/561/console shows a segfault
>> while updating to this commit.
>>
>> I'm going to rerun the build, just in case it was a once-off. I'll
>> report back when it's done.
>>
>> Here's the top part of the stack; see the URL for full details:
>
> http://build.squeak.org/job/SqueakTrunk/562/console shows it happening
> again. So either something's very badly wrong, or something's very
> badly wrong just on that slave. (But you'll see in its history that it
> can run builds.)
>
> frank
>