8 years ago.

Compiler crashing with internal errors has taken all my code with it..

Hello:

I was attempting to compile a program I have been working on for last three or four weeks and it failed with "internal errors" . I tried again and it failed with a new error having to do with lwip (and internal to lwip). Nothing to do with ethernet had been changed in my program for several weeks. There was no reason for this error.

Thinking this was the result of some changes to mbed I updated the libraries and it deleted all changes I have made including deleting added source files and set the whole thing back to the example I had originally copied a month ago. All my work is gone and I am very frustrated. Besides adding hundreds of lines of code I also had to fix several mbed libraries to get them to work properly and those fixes also seem to be gone.

I obviously should have copied it before hand but was not expecting these problems. I am not aware of any foolproof way to back up a project.

Is there anyway to get this back to where it was at any point before today?

Also there does not appear to be any real support options for these problems, only the forums which often go unanswered.

If there is anyway to fix this please let me know: otherwise I certainly won't be using this again... Doug

2 Answers

8 years ago.

Quote:

I obviously should have copied it before hand but was not expecting these problems. I am not aware of any foolproof way to back up a project.

Export to ZIP is for sure a good idea. It gives you the backup, so you can make sure it is secured. Since the online compiler is free and you haven't gotten an SLA from mbed/ARM, you have no rights.

And in addition what helps is committing changes. This allows you to always go back to an old commit, although you still rely on mbed not throwing away stuff.

Quote:

Is there anyway to get this back to where it was at any point before today?

Try mailing to support@mbed.org, probably your best shot, although I don't know if they can and will help with something like this.

Quote:

If there is anyway to fix this please let me know: otherwise I certainly won't be using this again... Doug

Of course that is your decision, however while in the past mbed has royally screwed up with backups, in this case you choose the option to delete all your changes and go back to the original without keeping a copy of the old version. I understand that it really sucks, but you can't really blame mbed for that.

I did not intentionally delete all my changes: according to what I could find I thought I was updating the libraries and certainly not deleting my own code. The program was originally copied from an example and renamed so I had no expectation it would even be aware of the original example let alone would wholesale replace main.cpp and delete six additional (user) files without warning.

Also note that this whole episode was in response to an error that suddenly appeared in library code: not in my own program. The library revision was an attempt to get it to function again. I had made no change that in anyway touched the code reported in error. This was in the lwip library which I am familiar with and all errors pointed to an internal problem with an object library.

I was unaware there was a zip option and still don't see it. I was also unaware the commit/revision functions worked because they were useless the last time I looked at them though this was likely 6 months ago.

While I should have made a back up copy this is not easy to do and if you look at what little documentation there is I was under the impression that it was actually tracking the changes from session to session by itself. Blame the operator if you want but if it's too buggy and unstable it isn't suitable for anything serious. It took probably a dozen hours to get one of the mbed component libraries to function properly since the library was obviously written by someone who had no clue how interrupts work on a uC. I was intending to make those changes available but I really don't see the point in going through that again and I would likely be further ahead to write my own drivers based on the C examples from ST with cube/eclipse/gcc.

Doug

PS: I emailed as a last hope, thanks.

posted by Doug Morgan 13 Nov 2016

Well the only ones who can help you are mbed staff, and for that I would try mailing.

posted by Erik - 13 Nov 2016
8 years ago.

What I do are regular backups via ZIP ofr uVision downloads of my project. Of course I do regular mbed checkins to save each step of my development. The mbed source management system uses "Mercurial" which allows you to install Mercurial on your PC/Mac and to download the entire project with all history information via the Mercurial "hg clone" command. Helmut

I sure do miss the ZIP option

posted by Kevin Braun 14 Nov 2016