| library or example for good logging [message #1694276] |
Mon, 04 May 2015 03:22  |
Eclipse User |
|
|
|
Hi,
I would like to get more detailed information about an executed transformation.
e.g. I would like to see, in which order the functions/mappings were executed and the depth of the executed functions (main() is depth 0, a function called by main has depth 1, ...), preferably with different logging-levels
Does some kind of library already exists, can somebody give me some example?
I was thinking about an abstract function/mapping which feeds some logging-functions/library and all other function/mappings inherit from the abstract one.
But I am not sure if that is possible, also I dont want to reinvent the wheel. The name of the inheriting function should be logged too, which I am not able to do.
|
|
|
| Re: library or example for good logging [message #1694356 is a reply to message #1694276] |
Mon, 04 May 2015 12:31  |
| Eclipse User |
|
|
|
Hi
The standard launch dialog gives you the option to create a trace model
which contains a lot of detail.
Hot off the press for Mars is a profiling/coverage capability. It's
hidden away obscurely as a select other at the bottom of the generic
tracing tab.
Regards
Ed Willink
On 04/05/2015 08:22, Thomas Busch wrote:
> Hi,
>
> I would like to get more detailed information about an executed
> transformation.
> e.g. I would like to see, in which order the functions/mappings were
> executed and the depth of the executed functions (main() is depth 0, a
> function called by main has depth 1, ...), preferably with different
> logging-levels
>
> Does some kind of library already exists, can somebody give me some
> example?
>
> I was thinking about an abstract function/mapping which feeds some
> logging-functions/library and all other function/mappings inherit from
> the abstract one. But I am not sure if that is possible, also I dont
> want to reinvent the wheel. The name of the inheriting function should
> be logged too, which I am not able to do.
>
|
|
|
| Re: library or example for good logging [message #1694409 is a reply to message #1694356] |
Tue, 05 May 2015 03:53 |
| Eclipse User |
|
|
|
|
The trace model is generally very good, but I do have a lot of functions which are not direct mappings and a lot of crazy logic. That decisions and function callings are not visible in the trace model. I assume that means I have to make me an individual logging
|
|
|
Powered by
FUDForum. Page generated in 0.42197 seconds
Home