Build fail in ida about snowman

[yegord]

Hi, thank you for reporting this.
I uploaded new binary packages for v0.0.7, they should work now.
(Apparently, stripping was a bad idea.)

Concerning your build attempt,

1. you must use Visual Studio 2010,
2. you muse use --config Release together with cmake --build . (there is a note on this in the build instructions).

[techbliss]

It builds okay in visual. 2013.
I am not Cmake expert but aint the

You can choose a build mode (Debug, Release, RelWithDebInfo, or MinSizeRel):
-D CMAKE_BUILD_TYPE=Release
the configure for Release.
its however disrergarded when building.Starts with Debug

i cant seem to find anything on
--config Release
Also can you tell how to turn stripping off so i can trry build it also.

[yegord]

-D CMAKE_BUILD_TYPE=Release is disregarded when msbuild is used. Use --config.

[techbliss]

okay thx .
Latest build you added are working.
You can close issue.

[techbliss]

Reason for reopening the issue, is that i have builded @nihilus version with mips support.
https://github.com/nihilus/snowman
It crashed in ida, just as your pre version did before you fix stripping.
Can you tell what you did with stripping, so i can rebuild and test the decompiler with mips support.
I am building it in vs studio.
regards

[nihilus]

@techbliss did you test building from @yegord as well? Else we should close this and open issue on my repo IFF yegords works fine.

[nihilus]

Especially interesting since AFAIK the support for C++11 features is limited in VS 2010, else Id build if myself.

[techbliss]

@yegord releases works fine, but this is the same issue as i started here, and in the end mips would hopefully be pulled with the original.
you forked it before it was fixed
So hope its okay ill ask here.

[yegord]

The problem was that I did stripping. I stopped doing it, and everything started working again.
In other words, the problem was in my release script, not somewhere in the build process.

[techbliss]

Cmake is not for the faint of heart can you pinpoint me to the right line.
@nihilus unfortunately fork your repo before it was fixed.

[yegord]

My buildbot that produces binaries for my homepage succeeds with the following:

'cmake' '-DCMAKE_INSTALL_PREFIX=install-prefix' '-G' 'Visual Studio 10' '-DQT_NAMESPACE=QT' '-DIDA_PLUGIN_ENABLED=YES' '../snowman/src'
'cmake' '--build' '.' '--config' 'Release'
'cmake' '--build' '.' '--config' 'Release' '--target' 'install'

(qmake.exe is in the %PATH%, BOOST_ROOT is specified in the environment variable.)

[techbliss]

I have tried building @yegord master latest and still getting the error in ida.
I use build lines mentioned

'cmake' '-DCMAKE_INSTALL_PREFIX=install-prefix' '-G' 'Visual Studio 10' '-DQT_NAMESPACE=QT' '-DIDA_PLUGIN_ENABLED=YES' '../snowman/src'
'cmake' '--build' '.' '--config' 'Release'
'cmake' '--build' '.' '--config' 'Release' '--target' 'install'

Stansdalone snowman works without flaws.
In ida snowman shows, but if i click a function ida crash.just like before.

i have analyzed the crashdump of the error.maybe some clues.
http://pastebin.com/a8DJm3Si

[yegord]

Sorry, no clues. Works for me. I am afraid, without a shell access I will not be able to say much.

[techbliss]

Yes i have tried almost all.

well if your on skype and have time sometime in the next days you can add me zadow28.
Or maybe set up a gitter for your repo.
https://gitter.im/
But leave the issue open for now.
Now im gonna hit the bed.

[yegord]

@techbliss BTW, taking into account that you managed to build @nihilus's fork with MSVC 2010, although it currently can't be built with MSVC 2010, I draw a conclusion that you built not with MSVC 2010, and this is probably why you get crashes.

[techbliss]

I never tried building it with 2010, only 2013(see third post) and 2015. Snowman works outside ida both versions.cant see why it should be builded only with 2010
Should it ?
I have no clue.but cant see why 2010 should work better.
Or harder to build. Think @nihilus needs the servicevpacks to make itvwork prober.

[yegord]

MSVC 2010 has one runtime library, MSVC 2013 has another runtime library. If you have IDA using one runtime library (the one of MSVC 2010), and its plugin using another runtime library (the one of MSVC 2013), things start go wrong.

[yegord]

https://github.com/yegord/snowman/blob/master/doc/build.asciidoc#notes-on-building-ida-plug-in — item 2.

[techbliss]

Ahh get it msvc100.dll contra 130 mismatch = heap error
However ill give it a go on 2010 tommorow.

[nihilus]

@techbliss @yegord seems that MSVC 2010 have issues with namespaces and lambda functions. However it is now fixed for MIPS/Allegrex.

[techbliss]

Okay now i have rebuilded everything @nihilus version with vs2010(RELEASE), with vs studio ,that one crashed in ida also.
since there have been issues with getting the decompiler to actuelly select Release version, adressed here nihilus#31
i tried building it as Relwthdebuginfo, and that version works flawless in ida.Maybe Build your build bot skips Release part.

But els i can confirm that Snowman Mips is working in ida.

prebuild releasewthdebuginfo with MIPS https://mega.nz/#!7xlwGTZY!bRJiioDOmC1KlygY64Dn35dXkAuE2O36GOFGDyyoHfg

[yegord]

Hmm. Release and RelWithDebInfo must produce literally the same code.
Do the .plw files differ?

[techbliss]

yes there is a huge difference
release = 2 594 KB(2.5mb)
release with debug info = 5 184 KB
here are both versions.I removed *pdb generated files to save space in RelWithDebInfo folder
https://mega.nz/#!b1EUSLrI!LYNNoRgglRsr8HF_8jSzuRRxJ1hID2AV4SjHvsFIMW0

[techbliss]

Woot i found error.
Release success.
after your explanation of the run time.
I had the heap error on other apps, and that send me on a investigation.
I developed alot of qt apps for ida,and sometimes i make newer branches of PyQt4 for ida pro..
And newer before resently did i had any trouble with those versions.

so i builded windows QT4.8.7 with from scratch with correct vs version.
then latest Qscilla2.with correct vs vs version.
then latest PyQt4 with correct version.that one was really persistence to build as 2008 ( same as prebuild version).

in the end all same version. Msvcr100.dll
No more runtime errors.
So this issue helped me more than one way.
Issue can be closed
Thx and regards