Debugging ASCEND: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
There is a '''[http://ascendbugs.cheme.cmu.edu Bug tracker]''' for ascend outside of this wiki. | There is a '''[http://ascendbugs.cheme.cmu.edu Bug tracker]''' for ascend outside of this wiki. | ||
Some useful additional information relating to debugging: | |||
* about test suites (see [[CUnit]]) | |||
* using [[Valgrind]] to track down segfaults and memory leaks | |||
Also to be added here: | Also to be added here: | ||
* about Buildbot (currently inactive/offline) | * about Buildbot (currently inactive/offline) | ||
* using GDB | * using GDB | ||
* correct use of SVN during debugging on the trunk | * correct use of SVN during debugging on the trunk | ||
* using 'pygtk/ascdev' and 'tcltk/asc4dev' from within your working folder | * using 'pygtk/ascdev' and 'tcltk/asc4dev' from within your working folder | ||
Revision as of 06:41, 15 February 2011
The content from this page was lost in a recent server failure. We will be working to restore this content as soon as possible.
Reporting a bug
There is a Bug tracker for ascend outside of this wiki.
Some useful additional information relating to debugging:
Also to be added here:
- about Buildbot (currently inactive/offline)
- using GDB
- correct use of SVN during debugging on the trunk
- using 'pygtk/ascdev' and 'tcltk/asc4dev' from within your working folder
- possible library wrong-loading issues: export LD_LIBRARY_PATH=~/ascend for example,