Does VW run on intel core 2 duo (Windows)?

I received a comlaint that my VW 7.4.1 app doesn't run on intel core 2
duo e6600, Windows XP. Anyone experienced this too? The message says:
Unhandled Exception: Bad Argument 5. Unfortunately I don't have such a
machine to test it myself.

Thanks in advance
Andre

I tried running VisualWorks -- and our packaged application – on the
new Intel processors:
http://www.cincomsmalltalk.com/userblogs/runarj/blogView?showComments=true&entry=3334319381

I had no such problems as you describe. I think I have the same
version (e6600) as you do.

Runar Jordahl

On Jan 13, 2007, at 11:28 AM, Andre Schnoor wrote:

> The message says: Unhandled Exception: Bad Argument 5.

To me that looks like a generic VM error: some primitive failed  
because the 5th argument passed in was of inappropriate type.

It seems like something needs to be fixed at the image level. (Or  
perhaps the .im was corrupted in that particular installation?)


R
-

Hmm. I wonder where the message "Unhandled Exception: Bad Argument 5"
stems from. Is this a regular UHE from VW or is it a message from
Windows? Unfortunately I don't have a screenshot.

Andre

Runar Jordahl schrieb:

On Jan 13, 2007, at 12:20 PM, Andre Schnoor wrote:

> Hmm. I wonder where the message "Unhandled Exception: Bad Argument  
> 5" stems from. Is this a regular UHE from VW or is it a message  
> from Windows? Unfortunately I don't have a screenshot.


It is a VM level message sent to the image, see

SystemError class>>installSystemErrors
        "Build the set of system errors."
        | list |
        list := Array new: 100.
        list at:  1 put: (self named: #'generic error' parameter: nil).
        list at:  2 put: (self named: #'allocation failed' parameter: nil).
        list at:  3 put: (self named: #'C allocation failed' parameter: nil).
        list at:  4 put: (self named: #'bad argument' parameter: nil).
        ...


So I repeat: the VM is complaining that the image screwed up a  
primitive call.


R
-

>
>
> So I repeat: the VM is complaining that the image screwed up a  
> primitive call.
>

For more context: use the RB to find methods with strings matching  
'*Bad Argument*', you will see how this error is passed or handled in  
several primitive methods.


Can you get a hold of the error.log of that crash?


R
-