Is this program made for slow people or is it just me ?
I've used HDT 1.0 up untill now, and wanted to test sigasi 2.0. But here after 6 hours I have come no closer to that.
here is a list of problems I've run into:
1: When I build after I've added my Library the program can have a tendency to crash with wierd bugs or die silently.
2: When i type code the program can suddently lock up completely.
3: When I try to type, in this case a IF sentence, I ctrl+space to complete it. It takes up to 15 seconds for the box selection to come so i can complete it. (way faster just to type it my self)
4: When I move around in the preference menu somtimes it just locks up or reports a bug problem and crashes.
5. Quick fix dosnt work either, have a few signals which are new, and i try to press ctrl+1 and nothing happes I try and do it through the rightclick menu and that dosnt work either.
6. Cant realy used the Error section for anything since it shows 605034 errors on a project I know works.
besides the obvious bus, crashed and other things which can drive a person to commit suicide. Its a nice program and a good initiative to make a good editor for HDL community.
regards Geo
- Forums:
Performance
Hi Geo,
If you have so many errors there is probably a problem with library mapping. If you send me your project, I will check what goes wrong. Apart from the very first build, Sigasi 2 should be faster than Sigasi 1.0.
Thanks for your feedback,
Hendrik.
see next post, should have
see next post, should have been a reply to this :)
Errors
Well I cant give you a copy of my code sorry.
But the many errors i encounter is when I add the Xilinx thirdparty libraries (I use ISE design suit 13.1).
I follow your guide and i can add them but after the system rebuilds I have tons of errors or the program crash. The only errors I have in my code is missing libs (thoes from Xilinx before I add them) and deprecated libaries but thoes are warnings.
Ive been browsing around a little in this forum and some of the errors I see others have seen also.
Ps Sorry for the first post, I was somewhat frustrated given that I have worked with 1.0 without fault and suddently I Hit wall after wall when trying to setup this new version.
UPDATE:
This morning when I stated the program I forgot to loginto my network drive (where the xilinx libraries are) and the program started without being able to find them. I then logged in and refreshed my workspace and everything seems to work now. The only errors I have are thoes I've made my self and the excess 1000+ errors are gone.
Now a function to disable some warnings would be good feature, since some warnings for old VHDL code are unavoidable and uninterresting.
UPDATE 2:
Started working with it now, and quick fix still dosnt work. Dont know why but both the shortcut and the menu item dosnt do anything. (This is one of the main features that does I want to use this program)
UPDATE 3:
Been working with the program for 3 hours when i tryied som refactoring and got a "reference null" bug. Click ok and continued to work. 30 seconds later the program crashed/closed silently. When I got it up and running again all the libraries references where gone. tried a rebuild and all my 65000+ errors are now back.
UPDATE 4:
While typing I hit this bug (I've also sendt it throught your bug report feature. However this bug arrived what felt like the text editor not able to keep up. I had just pressed save ctrl+s and continued to work and the whole editor locked up on me (happens quit alot and is realy annoying) and then the bug report appered.
The bug kept reapering everytime I clicked on a signal difinition either std_logic or unsigned ect.
BugReport [ version=2.1.1.201111241152 pluginName=org.eclipse.core.jobs pluginVersion=3.5.100.v20110404 stacktrace= at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eStructuralFeature(BasicEObjectImpl.java:739) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eObjectForURIFragmentSegment(BasicEObjectImpl.java:557) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.getEObject(ResourceImpl.java:780) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.getEObject(ResourceImpl.java:756) at org.eclipse.xtext.resource.XtextResource.access$1(XtextResource.java:1) at org.eclipse.xtext.resource.XtextResource$1.getEObject(XtextResource.java:102) at org.eclipse.xtext.resource.DefaultFragmentProvider.getEObject(DefaultFragmentProvider.java:26) at org.eclipse.xtext.resource.XtextResource.getEObject(XtextResource.java:286) at org.eclipse.xtext.linking.lazy.LazyLinkingResource.getEObject(LazyLinkingResource.java:282) at org.eclipse.xtext.ui.editor.occurrences.DefaultOccurrenceComputer$1.exec(DefaultOccurrenceComputer.java:115) at org.eclipse.xtext.ui.editor.occurrences.DefaultOccurrenceComputer$1.exec(DefaultOccurrenceComputer.java:1) at org.eclipse.xtext.util.concurrent.AbstractReadWriteAcces.readOnly(AbstractReadWriteAcces.java:32) at org.eclipse.xtext.ui.editor.model.XtextDocument.readOnly(XtextDocument.java:78) at org.eclipse.xtext.ui.editor.occurrences.DefaultOccurrenceComputer.createAnnotationMap(DefaultOccurrenceComputer.java:86) at com.sigasi.hdt.vhdl.ui.editor.VhdlOccurrenceComputer.createAnnotationMap(VhdlOccurrenceComputer.java:4) at org.eclipse.xtext.ui.editor.occurrences.OccurrenceMarker$MarkOccurrenceJob.run(OccurrenceMarker.java:122) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) message=An internal error occurred during: "Mark Occurrences".
]
Regards Geo
Feedback
Hi Geo,
Most of your issues will be fixed in the upcoming release (if all goes well, later this week).
It is probably best to disable occurrence highlighting for now.
Thanks for the feedback,
Hendrik.
Ok, I've update to the lates
Ok, I've update to the lates release.. and nothing have changed.
This program cannot be used with my working enviroment in anyway what so ever.
Sorry to say but this is not a finished product I would use or recomend to any of my collegues, and its its deffently not something worth a 1000+ euros.
/Geo
Hi Geo, I'm mailing you to
Hi Geo, I'm mailing you to help you find the problem.
Post new comment