Author Topic: Configure Error Parsing not working?  (Read 1429 times)

warnerrs

  • Senior Community Member
  • Posts: 114
  • Hero Points: 4
Configure Error Parsing not working?
« on: September 30, 2015, 01:10:12 pm »
My user defined error parsing regular expressions aren't working in V20.

I tried removing my .slickedit/ folder and I re-imported just my error parsing regexes, but they still didn't work.

Quote
OS: Linux
OS Version: Red Hat Enterprise Linux Workstation release 6.4 (Santiago)
Kernel Level: 2.6.32-358.23.2.el6.x86_64
Build Version: #1 SMP Sat Sep 14 05:32:37 EDT 2013
Processor Architecture: x86_64

Project Type: SystemVerilog
Language: .sv (SystemVerilog)
Encoding: Automatic

Installation Directory: /user/ryanw/apps/slickedit/20.0.0.3/
Configuration Directory: /user/ryanw/.slickedit/20.0.0/

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4691
  • Hero Points: 379
Re: Configure Error Parsing not working?
« Reply #1 on: September 30, 2015, 04:48:11 pm »
Please post your ErrorRE.xml. As long as your addition has some sample text, that should be all we need.

Thanks
« Last Edit: September 30, 2015, 06:13:19 pm by Clark »

warnerrs

  • Senior Community Member
  • Posts: 114
  • Hero Points: 4
Re: Configure Error Parsing not working?
« Reply #2 on: September 30, 2015, 06:22:33 pm »
Here is a sample to test against. It matches pattern "VCS Error 4" from the attached options file. That pattern works in the expression editor when I click "Validate". It just doesn't do anything when I actually run my build script.
Quote
Ignore this

Error-[SE] Syntax error
  Following verilog source has syntax error :
  "../rtl/timer.sv", 26: token is ','
                     task slv_get_cmd,
                                      ^

And this

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4691
  • Hero Points: 379
Re: Configure Error Parsing not working?
« Reply #3 on: September 30, 2015, 06:41:56 pm »
I'm noticing some initialization issues. Doesn't seem to be new (reproduced in v19 and v20). I added a regex and it only works after I run the "cursor-error" command in the Build window. Until then, it does nothing.

We will look into this.

Thanks for noticing this problem.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4691
  • Hero Points: 379
Re: Configure Error Parsing not working?
« Reply #4 on: September 30, 2015, 06:59:10 pm »
This will be fixed in beta 3.

The problem was an initialization issue. The error regular expression are not loaded by the next-error command. Only the cursor-error command loads them.