issue running watir on 64 bit winxp

[Justin Rohrman]

I am having an issue running watir test scripts on 64 bit winxp that
were previously working on 32 bit winxp (both envs 32 bit using IE7).
Whenever the test script is run, it returns this error:

ruby Test.rb

(eval):12: [BUG] Segmentation fault
ruby 1.8.6 (2007-09-24) [i386-mswin32]


This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.

Exit code: 3

I am running ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] and
watir-1.5.1.1192.

Has anyone seen this before?

Thanks!

 

[Luis Lavena]

I am having an issue running watir test scripts on 64 bit winxp that
were previously working on 32 bit winxp (both envs 32 bit using IE7).
Whenever the test script is run, it returns this error:

ruby Test.rb

(eval):12: [BUG] Segmentation fault
ruby 1.8.6 (2007-09-24) [i386-mswin32]

This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.

Exit code: 3

I am running ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] and
watir-1.5.1.1192.

Has anyone seen this before?

AFAIK, noone.

Sometimes mixing 32bits applications with 64bits environments don't
work out of the box (and sometimes Windows on Windows - WOW64) don't
catch all these things.

If watir is interfacing DLL/APIs from Windows, then is highly likely
there are some changes of implementation or answers from these API
that make Watir/Ruby crash.

I you contact the Watir project [1] and try to include all the
information possible, also the test script you're trying to run.

[1] http://wtr.rubyforge.org/

Regards,

 

[debuke]

I am having the same problem:

C:\dev\Utility\scripts\ruby>ruby login.rb
c:/apps/ruby/lib/ruby/gems/1.8/gems/watir-1.5.4/./watir/frame.rb:32:
[BUG] Segme
ntation fault
ruby 1.8.6 (2007-09-24) [i386-mswin32]

This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application's support team for more information.

------------
here is my (simple) script that i'm running on xp sp2, ie7:

require "watir"

testsite = "https://my.site.com/"
ie = Watir::IE.new
ie.goto(testsite)
ie.text_fieldname, "UserName").set "myname"
ie.text_fieldname, "Password").set "mypassword"
ie.text_fieldname, "Client").set "myclient"
ie.buttonid, "Submit").click
ie.wait
expected_url = testsite + "Home/UserHome.asp"
if ie.url == expected_url
ie.spantext, "View/Modify Items").click
ie.wait
ie.radioid, "Filter").click
ie.wait
ie.select_listname, "Filter").click
ie.select_listname, "Filter").select("saved filter")
ie.wait
ie.buttonid, "Submit").click
end

this works on xp sp2 machines that are running ie6, oddly enuff...

 

[Luis Lavena]

I am having the same problem:

C:\dev\Utility\scripts\ruby>ruby login.rb
c:/apps/ruby/lib/ruby/gems/1.8/gems/watir-1.5.4/./watir/frame.rb:32:
[BUG] Segme
ntation fault
ruby 1.8.6 (2007-09-24) [i386-mswin32]

This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application's support team for more information.

------------
here is my (simple) script that i'm running on xp sp2, ie7:

require "watir"

testsite = "https://my.site.com/"
ie = Watir::IE.new
ie.goto(testsite)
ie.text_fieldname, "UserName").set "myname"
ie.text_fieldname, "Password").set "mypassword"
ie.text_fieldname, "Client").set "myclient"
ie.buttonid, "Submit").click
ie.wait
expected_url = testsite + "Home/UserHome.asp"
if ie.url == expected_url
ie.spantext, "View/Modify Items").click
ie.wait
ie.radioid, "Filter").click
ie.wait
ie.select_listname, "Filter").click
ie.select_listname, "Filter").select("saved filter")
ie.wait
ie.buttonid, "Submit").click
end

this works on xp sp2 machines that are running ie6, oddly enuff...

OK, I got missed interpretations of your post:

"here is my (simple) script that i'm running on xp sp2, ie7:"

That is xp sp2 32bits, or what?

Got messed up since you finish your post with: "this works on xp sp2
machines that are running ie6, oddly enuff..." ...

So: have you tried xp sp2 32bits with IE7, or just with IE6? in any
case, I suggest you try IE7 on 32bits or check what is actually doing
the offending watir file, so we can determine if:

- is a API call to some DLL that behaves differently in 64bits
- is a change in the API of IE6 versus IE7.

Regards,