#62 Debugger doesn't work on Linux 32bit

[Nathan Tenney]

The debugger fails to recognize many commands on Linux systems.

06/02/08 11:03:14 changed by dchassin Âś
Some of the problems are gone, but there are still situations where the command isn't recognized but should be. Recommend exhaustive testing and debugging to track down and document the issues.

[David P. Chassin]

• status changed from new to assigned

[David P. Chassin]

• priority changed from major to minor

[David P. Chassin]

• priority changed from minor to major
• status changed from assigned to accepted
• milestone set to Release src-2_0_0

[David P. Chassin]

• owner changed from dchassin to mhauer
• status changed from accepted to assigned

This certainly is true when using the --debugger with runtime classes on linux. It tried to use 'cl' instead of 'gcc', which means that it thinks it's debugging on Windows. A simple case the exhibits this problem is to use the command

% cd trunk/core/test
% gridlabd --debugger timestamp.glm

[David P. Chassin]

• milestone changed from Release src-2_0_0 to Version 2.1 Stable

[Matthew Hauer]

debugger.conf explicitly sets "use_msvc=1". Inline platform checks are needed to determine if this logic should be used at runtime.

[Matthew Hauer]

r1772 updates the two debugger.conf files with msvc-specific settings, which will avoid 'poisoning' the session environment settings on non-Windows platforms. Uncertain if this is a fix on *nix platforms.

[David P. Chassin]

• owner changed from mhauer to dchassin
• version changed from 2.0 to trunk
• type changed from defect to task
• milestone changed from Version 2.1 Stable to Unscheduled

The implementation of the debugger needs to be moved to a module and redesigned.

[David P. Chassin]

• status changed from assigned to closed
• resolution set to duplicate

This will be addressed by #601.