Re: [Gems-users] Opal compilation and traces


Date: Mon, 30 Oct 2006 12:32:00 -0600 (CST)
From: Mike Marty <mikem@xxxxxxxxxxx>
Subject: Re: [Gems-users] Opal compilation and traces
The default directory appears to be hard-coded in several spots in the
Opal codebase:

maya(16)% find . -name "*.C" -exec grep -l 'scratch.local' {} \;
./tester/SCCS/s.makeipage.C
./tester/makeipage.C
./trace/SCCS/s.branchfile.C
./trace/SCCS/s.memtrace.C
./trace/SCCS/s.tracefile.C
./trace/branchfile.C
./trace/memtrace.C
./trace/tracefile.C

--Mike


> Hi All,
>          In opal/README the following is specified:
>
>    # "data" should be a sym-link to somewhere with lots of space!
>    # trace start: outputfile is ./data/onem-latest
>    opal0.trace-start onem-latest
>
> I do have a symlink to scratch.local in simics_workspace/home/MOESI_CMP_NUCA
> (thats where I am running simics from) pointing
> to a directory, but when I run "opal0.trace-start opal-testrace" command I
> get the following
> errors:
>
> opening file /scratch.local/opal-testtrace
> opening file /scratch.local/mem-opal-testtrace
> [1]     PC 0x18c358     NPC 0x18c35c    ctx 0x81b
> sh: /scratch.local/opal-testtrace: No such file or directory
> sh: /scratch.local/mem-opal-testtrace: No such file or directory
> .......
>
> Also if I add printf's in the opal code and then make clean and rebuild
> opal, I don't see the changes taking place. What could the problem be?
>
> Any kind of help is appreciated.
>
> thanks,
> Mishali
> Undergraduate Student, UCLA
>
[← Prev in Thread] Current Thread [Next in Thread→]