Next: , Previous: Customizing, Up: Top

8 Submitting a problem report

If you run into problems with ECB you should first take a look into

If your problem(s) still remain you can/should send a problem report to the ECB mailing list ECB offers you a command which does all necessary for you to send a problem report. Just call ecb-submit-problem-report! Please read the documentation of this command, see Interactive ECB commands.

IMPORTANT: Cause of extra appearance of SPAM in the mailing-lists, SourceForge has changed its policy: Now it is only possible to post to the mailing-list for users who have subscribed this mailing-list. So please be aware you will not be able to send comments, bug reports and improvement suggestions before you have subscribed the ECB-mailing-list. See the section "Mailing-list" at the ECB-website at how to do this.

If you think there are problems concerning parsing-results for certain sources supported by semantic then you should call ecb-dump-semantic-toplevel for the problematic source-buffer BEFORE you call ecb-submit-problem-report because this “dump”-command generates for the current-buffer a new buffer with name “*ecb-tag-dump*” which contains all semantic-tags for this source. The contents of this “*ecb-tag-dump*” will then autom. be added to the problem-report generated by ecb-submit-problem-report!

This command creates a problem-report buffer for you. After that you get a menu “Mail” (dependent on the mail-package used, the menu can have a different name) with commands to send the problem report. But for this the variable mail-user-agent must be configured right for your system. If you canīt get working this mechanism you can simply copy the whole problem-report buffer after filling it out and sending it with your standard mail-client to!

Please read also the documentation of the option ecb-debug-mode and switch on the debug mode of ECB (also available in the Help-menu of ECB!) before submitting a problem-report!