Re: [eq-dev] eqPly build for Windows 7 x64

[Stefan Eilemann]

On 19. Dec 2011, at 17:22, burn [via Software] wrote:

> Hi, I am absolutely newbie to the Equalizer.
> I tried to build eqPly example from sources (Window 7 x64, VS 2010, Equalizer-0.9.3), but got an error:

I'm not sure if 0.9.3 supported Win7 and VS2010. In any case, why don't you use a more recent version?

Cheers,

Stefan.

--
View this message in context: http://software.1713.n2.nabble.com/eqPly-build-for-Windows-7-x64-tp7108710p7108734.html
Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com.

_______________________________________________
eq-dev mailing list
eq-...@equalizergraphics.com
http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev
http://www.equalizergraphics.com

[Stefan Eilemann]

Hello,

On 19. Dec 2011, at 19:10, burn [via Software] wrote:

> Ok, Stefan, thanks. I've installed Equalizer 1.0.2 (last major release on site) and still have the errors:

Ok, better already. I missed the VS2010 part - We're using 2008 here so I can't reproduce and fix it here. The error comes from the shader strings missing in the executable. There should be a file examples/eqPly/vertexShader.glsl.cpp in your build directory which should be build and linked against the eqPly executable. Can you verify that this is happening, and that the file contains the vertexShader_glsl string?

HTH,

Stefan.

--
View this message in context: http://software.1713.n2.nabble.com/eqPly-build-for-Windows-7-x64-tp7108710p7111062.html

[burn]

Hi, Stefan.
Build was successful, but in runtime is still corruption in /debug.h/ , line
69:

/Critical error detected c0000374
Windows has triggered a breakpoint in eqPly.exe.

This may be due to a corruption of the heap, which indicates a bug in
eqPly.exe or any of the DLLs it has loaded./

The code in this line is allocation string:

/return std::string( typeid( *object ).name( ));/

The problem is allocation of string. Have you met such trouble and have you
any idea to fix it?

--
View this message in context: http://software.1713.n2.nabble.com/eqPly-build-for-Windows-7-x64-tp7108710p7117090.html

[cpapado]

This is a very interesting coincidence.

I am compiling an equalizer app that I previously developed in Xcode for
windows.

I am using VS2008 (but also tried in 2010) and compiling for 32 bit and I am
getting EXACTLY the same runtime error (basically the RTTI name() call on
the type_info struct) returns a bad_ptr and stuff goes belly up from there).

This is using the latest 32 bit 1.0.2 release from the "major releases"
section of the site.

Any ideas Stefan?

Thanks!

-Charilaos

--
View this message in context: http://software.1713.n2.nabble.com/eqPly-build-for-Windows-7-x64-tp7108710p7117150.html

[Stefan Eilemann]

Hi guys,

It would really help tremendously if you describe more detail on how to reproduce these bugs, e.g.:

- Does it happen in one of the examples? If yes, under which conditions? If no, what are you doing to cause it?
- Provide a stack trace leading to this bug
- Ideally open an issue to paste in all this info

It *could* be that you're having a null pointer somewhere which gets dereferenced.

Cheers,

Stefan.

--
View this message in context: http://software.1713.n2.nabble.com/eqPly-build-for-Windows-7-x64-tp7108710p7117864.html