Debugging ASCEND

From ASCEND

We use the Mantis bug tracker located at http://ascendbugs.cheme.cmu.edu/.

• Visit the ASCEND Bug Tracker now.

Contents 1 What to do if ASCEND crashes 2 Notes when using Mantis 2.1 Linking from the Bug Tracker to this Wiki 2.2 Linking for the Bug Tracker to ViewCVS 2.3 Linking subversion commits to the Bug Tracker 3 'Panic' reports 4 Other comments

[edit] What to do if ASCEND crashes

If you find that ASCEND has a crash, and you are using Linux, and you installed ASCEND using 'scons install', please try launching ASCEND through GDB. The best and easiest way to do this, owing to the fact that the ASCEND PyGTK GUI runs via the Python interpreter, is to type the following into a console

ASC_GDB=1 ascend

You will get a GDB prompt at which you should type

r

to start running the ASCEND PyGTK GUI. Then try to reproduce the crash. When the crash occurs, return to the console window and see what it says. You can type

where

to get full details of where the crash occurred. Unfortunately it's not so easy with Windows.

[edit] Notes when using Mantis

[edit] Linking from the Bug Tracker to this Wiki

If you enter text in a bug note or bug report with a pair of square brackets around it, the text will be transformed into a Wiki link, eg [[DebuggingAscend]] becomes DebuggingAscend.

[edit] Linking for the Bug Tracker to ViewCVS

If you enter 'changeset N' or 'rev N' or 'revision N' into the bug tracker, it will automatically be transformed into a link to the ViewCVS pages on the CMU server. This allows people reviewing a bugfix to quickly identify what changes were made.

[edit] Linking subversion commits to the Bug Tracker

We are yet to put this in place, however it is intended that if you make a subversion commit with the text 'fixed bug #200' or 'fixed bug 200' or 'bug 200' or 'bug #200' or even just '#200' then the commit message should be added as a bug note to the bug in question. And if the text includes 'fixed' it should mark the bug as resolved, with the resolution being 'fixed'. In anticipation of this, it is suggested that we start using this exact syntax in our commit messages.

See http://manual.mantisbt.org/manual.configuration.source.control.integration.php for more info.

[edit] 'Panic' reports

People using ASCEND who see a 'panic' message will be directed to BugReport on this Wiki, which will give further instructions.

[edit] Other comments

There are a heap of in-source 'TODO' comments collected by doxygen. We are yet to host the doxygen documentation for ASCEND -- coming soon.

Other items:

• do we need to keep the cvs versioning tag lines in the sources?
• do we need to keep the module ID string definitions in the sources?