Sun Studio 11 do not parse make output and create link to file?

Hi,

Running Sun Studio 11 and can only get file links in the output window when I run a make command that uses CC -g (debug option). We have integrated other tools into our make system (flexlint, cppUnit..) and even though we make sure that the syntax is exactly the same as the compiler output and matches regular expression under tools->options->building->make settings->error expression, it doesn't work. Why do you have to debug compile to get sun studio to create a file link in the output window? Doesn't sun studio just parse the text from the make command?

example of flexlint output for which no link is created:

"/vobs/project/oss/fm/fm4/fm-fmalib/fmbal/fmaaulib/src/FMA_List.cc", line 440: Error 84: sizeof object is zero or object is undefined'?br>

example of make debug output for which we do get a link:

"/vobs/project/oss/fm/fm4/fm-fmalib/fmbal/SunOS5.10/inc/FMA_alarm_record.hh", line 1310: Warning (Anachronism):Info "static" is not allowed and is being ignored.

Regards,

Ola

[1056 byte] By [Anything] at [2007-11-26 10:44:54]
# 1
It probably worth filing a bug through bugs.sun.com. You can also try new CND module for NetBeans that generally does a better job than Sun Studio (except it has no debugging support yet): cnd.netbeans.org.
MaximKartashev at 2007-7-7 2:56:58 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 2
Yes.. but it is actually just the debug support that we want. We have this working in Eclipse with CDT for editing code but we would like to switch to sun studio because it's supports DBX as well.Regards,Ola
Anything at 2007-7-7 2:56:58 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 3

What I actually meant is the following:

- try cnd.netbeans.org and see if it solves your "goto error line" problem

- if it is, then you don't need to file a bug (well, unless you have a support contract, of course), next version of Sun Studio most probably will solve your problem

- if the problem you're experiencing is not solved in cnd, please file a bug and I'm sure next version of Sun Studio will have a better support for this.

Of course, setting up CND takes time and you might want to skip this step and file a bug at a sweep.

MaximKartashev at 2007-7-7 2:56:58 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 4

I'd second Maxim's suggestion: try NetBeans 5.5 with C/C++ Development Pack. The official release of NetBeans C/C++ Development Pack 5.5 has happened a few days ago. You can download it from

http://www.netbeans.info/downloads/all.php?b_id=2284

Some of the changes between the beta3 build and FCS are:

* Significant performance improvements in the code parser resulting in faster results in the Class View and Code Completion

* Programs now run in an external terminal (system dependent) by default. This allows better input control

* Significant performance improvement in the debugging module

* Significant functionality improvement in the debugging module

* New project type "C/C++ Project From Existing Code" which simplifies creating a project from existing code

* Macro support in code completion

* Hyperlink navigation for macro usages and #include directives

* Reformat code

* Code folding

* Code completion

All these features will appear in next Sun Studio release, so you can

consider NetBeans C/C++ Development Pack 5.5 as a preview of new

Sun Studio IDE.

NikMolchanov at 2007-7-7 2:56:58 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 5

Ola, are you still tracking this issue (its been awhile:-)

The reason you don't get your errors highlighted is because Sun Studio 11 doesn't

use the error expression. Its "inherited" and we can't hide it, but we use a different

method.

Your posting looks like you have at least some control over your error output. If so

then you can make your output display hyperlinks. The reason we don't use the

error expression is that our compilers have an option to emit HTML and that gives

us a chance to display more information (we display both a link to the error and an

"info" link which displays a popup).

If you can change your error output (perhaps with a wrapper script) so it generates

HTML then it *should* display the error as a hyperlink. To see the HTML output from

the compiler you need to set an environment variable

(SPRO_EXPAND_ERRORS=HTML). Then do a make (of course you'll need compiler

errors or at least warnings to see how they're handled).

gordonp999 at 2007-7-7 2:56:58 > top of Java-index,Development Tools,Solaris and Linux Development Tools...