Error when going live with the patching

[philoop]

ok it works aka doesnt crash

[philoop]

but still cant make no patch go live....

[johannes]

Sorry, I'm lost here, my Win8.1 x64 with latest Microsoft patches applied works fine.
I can only suspect an incomplete install (aborted download/unzip or install, or worse, file system integrity issues) of Axoloti.

[philoop]

sorry technobear and johannes for stealing ur Time ...2nd time reinstalling solved the Problem.
anyway kinda strange why that happend

[johannes]

Glad this is resolved!

[thetechnobear]

Cool,

did you reinstall the runtime to fix it?

Also can you check your antivirus logs, it would be useful to know if it was the culprit - some will quarantine files they think are suspicious.
Would be useful to know, as mighty reoccur or spear for others

Glad you can get back to patching

[philoop]

I also reinstalled the runtime but that didnt work.
Zonealarm had blocked arm-none-eabi but after fixing this it still wasnt working.
Only a fresh install of the editor helped.
I didnt restart windows the first time I reinstalled.....

[mexakin]

Hi and thanks philoop for also stepping in and telling your problems.
I am now home again and simply did try another reinstall again, it does go live now here again.

What I did different: I got 2 partinions on my one laltop harddrive C and D, I do install axoloti on my C program files, but this time i did install the runtime on the D partition and it did work.

Just for further info:

My windows is: Win 7 Professional Service Pack 1

Java and stuff I am right now not sure where to find, but if this is really important to you just say a word and I willl look it up.

Thanks for your kindly support, so now I am trying the midi clock stuff and get back with results.

[mtyas]

I've just had the same problem (win 8.1 x64) and resolved it by deleting the build folder in \Documents\axoloti folder.

[mexakin]

Had the problem again, dopnt knwo what issue is causing this, BUT you are right, i deleted the installation 3 times, nothing changed i got the error again, but when deleting my documents/runtime..blbalbalbaa folder it does work again now.

Just wanted to say that it seems to be the solution or workaround

[Inaba]

i just experienced thesame issue, and i solved it by going to my documents>axoloti>build and delete everything in that folder

[philoop]

I had the Problem again, and i can confirm the solution works:smiley:

[philoop]

third time mingw error...sigh ....i wonder what the cause is....

[philoop]

i just experienced thesame issue, and i solved it by going to my documents>axoloti>build and delete everything in that folder

4ourth time mingw32 error

[thetechnobear]

is the error still exactly the same as you had originally?

Win8.1 64bit java 8.65.....error first time:

Datum: 22.10.2015 18:44:58

Name des fehlerhaften Moduls: cc1plus.exe, Version: 0.0.0.0, Zeitstempel: 0x55772e0b
Ausnahmecode: 0xc0000005
Fehleroffset: 0x008bbe56
ID des fehlerhaften Prozesses: 0x1380
Startzeit der fehlerhaften Anwendung: 0x01d10ce8fb1fb4c1
Pfad der fehlerhaften Anwendung: c:\program files (x86)\axoloti_runtime\platform_win\bin..\lib\gcc\arm-none-eabi\4.9.3\cc1plus.exe
Pfad des fehlerhaften Moduls: c:\program files (x86)\axoloti_runtime\platform_win\bin..\lib\gcc\arm-none-eabi\4.9.3\cc1plus.exe
Berichtskennung: 3a6317d3-78dc-11e5-8332-448a5ba4fd59

if this happens again, rather than deleting the build directly, can you just try to delete the xpatch.h.gch file
and then try to go live, and see if this fixes it.

also can you confirm it does it with all patches e.g. even the tutorial patches.

the issue is, this is not an axoloti bug as such, its the compiler crashing... so we need to determine what it is thats causing the compiler to crash.

whats obviously odd, is that it appears to be working for you, for months at a time, then suddenly stops...
so something must change... Im guessing its not something as 'obvious' as immediately after you upgrade Axoloti, as you would notice this... so its something outside of axoloti.

are others getting this regularly?

seems odd, johannes doesnt seem to get it... as he uses windows most of the time. (I dont)

[hellcore]

I had this a fair amount today while testing out some new objects I have been working on. I'll try and see if there is any pattern when I continue tomorrow.

[philoop]

not really the 3 last times it had short message mingw32 error, sorry i didnt copied it, i will investigate further
its more like this

internal error in mingw32_.................................................: Attempt to access invalid address.

not soo urgent i guess, next time i will monitor closer what i did.

[johannes]

I haven't experienced this, maybe a the compiler was aborted somehow while generating the xpatch.h.gch file, but leaving a corrupt/incomplete file. Virus scanners are also suspect, quarantining the compiler, do you run any?

[philoop]

hmmmm @johannes
I'll try and see if there is any pattern when I continue tomorrow.

[thetechnobear]

I haven't experienced this, maybe a the compiler was aborted somehow while generating the xpatch.h.gch file, but leaving a corrupt/incomplete file.

yeah, thats what I was wondering.... if deleting the build directory fixes it, then it sounds like a file that used across builds.
but even then, its odd... since the gch wont be changing, unless the firmware is updated... so how does it 'suddenly' become corrupt, if it was working before.

anyway, would be nice to narrow down , which file in the build directory is causing the trouble, then work out why

btw, if deleting xpatch.h.gch doesn't immediately fix it, i.e. build still crashes, delete one file at a time in the build directory (remembering which you deleted!) and try again... though I think its only the gch file across builds.

(I guess we could have a 'secret key' e.g. pressing ALT whilst going live, which could perform a make clean, then make.)