On 11.02.2009, at 19:32, Rick Altherr wrote:
2) Unfortunately this also does not seem to help with my problems:
2.1) I still get two Saturn directories but only one start/stopSaturn was used
2.2) I still see no functions in the Saturn front end as if there is no debug information
3) I have now been using
3.1) The __attribute__((__no_instrument_function__)) decorator in main
3.2) initSaturn("/Saturn"); once as the first command in main
3.3) in one singlelocation in the application I invoke startSaturn() and endSaturn() to profile this specific section of code
There appears to be a bug where a call to endSaturn() doesn't actually stop the profiling, but rather switches to a new file. So, 2 files is "right".
The lack of functions in Saturn front end is harder to tell what when wrong. There should be a .sig file in the Saturn output folder. It should be generated when the program quits. If that file doesn't exist, the frontend will have no knowledge of what binaries were loaded in the process. If that file does exist, I'd need to see what is in it.
1) Here the files that are created after a single run of my binary "ljs-bin":
1.1) /Saturn/Saturn_profile_ljs-bin.000/SaturnTaskSignature
1.2) /Saturn/SaturnErrors.txt
1.3) /Saturn_profile_ljs-bin.000/ljs-bin.0.sat
1.4) /SaturnErrors.txt
2) I have instrumented the code as follows:
2.1) The __attribute__((__no_instrument_function__)) decorator in main
2.2) initSaturn("/Saturn"); once as the first command in main
2.3) A single code section invokes startSaturn() and endSaturn() to profile this specific section of code
3) I have attached the smaller files