Debugging ASCEND

From ASCEND
Revision as of 06:41, 15 February 2011 by Jpye (talk | contribs)
Jump to navigation Jump to search

The content from this page was lost in a recent server failure. We will be working to restore this content as soon as possible.

This page has been observed to be out-of-date. You can help to update the content, or search for a page containing newer information.

Reporting a bug

There is a 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:

  • 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,
Retrieved from "https://ascend4.org/index.php?title=Debugging_ASCEND&oldid=1791"