Error in Trace-buffering example

[Vidushi Vashishth]

>> The -B option should have a full path not a partial one. The $prefix
used when
>> building the BSP is missing.
>>
> >Did you use a full path? Is there an argument missing to the invocation?
>>

Adding full path to the -B option works. Turns out $prefix is not required
in the command.

>The link provided to our wiki does not have the full path. I am not sure
why ...

The wiki description also does not show the full path for fileio.exe and
init.o. I made changes to the command to overcome the errors. Should I
raise a ticket to make the changes?


However now on trying to run the trace link command (which follows) I am
encountering an error:

Command:

rtems-tld -C fileio-trace.ini -W fileio-wrapper --
-B/Users/vidushi/development/rtems/5/sparc-rtems5/erc32/lib/ -specs
bsp_specs -qrtems -mcpu=cypress -O2 -g -ffunction-sections -fdata-sections
-Wall -Wmissing-prototypes -Wimplicit-function-declaration
-Wstrict-prototypes -Wnested-externs -Wl,--gc-sections -mcpu=cypress -o
sparc-rtems5/c/erc32/testsuites/samples/fileio/fileio.exe
sparc-rtems5/c/erc32/testsuites/samples/fileio/init.o

Error:

error: /Users/vidushi/development/rtems/kernel/erc32: Invalid RTEMS path

According to the wiki documentation the rtems-path in the configuration
file should be set to the installed BSP.


Following is the [fileio-options] section of my configuration file:


;--------------------------------------------------------------------------

[fileio-options]

dump-on-error = true

;

; Tools

;

prefix = /Users/vidushi/development/rtems/5

rtems-path = /Users/vidushi/development/rtems/kernel/erc32

rtems-bsp = sparc/erc32

;

; Generator options.

;

gen-enables = enable

gen-triggers = enable


;--------------------------------------------------------------------------


My rtems-path does point to the installed BSP directory. I can't think of a
reason for this error.



On an unrelated note I am working on my proposal and would try to submit it
by end of today. For the past couple of days I have been trying to make the
trace-buffering example work and am hoping to solve the #2780 ticket. I
have also been going through the work of previous GSOC interns in the same
project trying to ascertain if I can carry forward from where they left
off. Hence I wanted to ask if trying to implement the live-tracing
functionality over several transport mechanisms would be a viable goal for
the proposal? Assuming it wasn't finished.



Also, given the paucity of time would you suggest that I finish the
proposal first or my patch for the aforementioned ticket.


References:

#2780 : https://devel.rtems.org/ticket/2780


Best,

Vidushi




On Mon, Mar 19, 2018 at 11:20 AM, Chris Johns <chrisj at rtems.org> wrote:

> On 19/03/2018 03:44, Joel Sherrill wrote:
> > On Mar 18, 2018 6:48 AM, "Vidushi Vashishth" <reachvidu at gmail.com
> > <mailto:reachvidu at gmail.com>> wrote:
> >
> >     Hello!
> >
> >     I am hoping to apply to Gsoc'18 for the runtime tracing project. I am
> >     following the RTEMS tracing documentation [1] and have been trying
> to run
> >     the fileio trace sample to familiarise with how traces are
> generated. I have
> >     set the rtems-path to the installed BSP erc32 in the
> fileio-trace.ini. The
> >     directory structure of my set up is the same as provided in the User
> manual.
> >     However while trying to link the fileio.exe I get a few errors:
> >
> >     Command:
> >
> >     sparc-rtems5-gcc -Bsparc-rtems5/erc32/lib/ -specs bsp_specs -qrtems \
> >
> >               -mcpu=cypress -O2 -g -ffunction-sections -fdata-sections
> -Wall \
> >
> >               -Wmissing-prototypes -Wimplicit-function-declaration
> >     -Wstrict-prototypes \
> >
> >               -Wnested-externs -Wl,--gc-sections -mcpu=cypress \
> >
> >               -o sparc-rtems5/c/erc32/testsuites/samples/fileio/
> fileio.exe
> >     sparc-rtems5/c/erc32/testsuites/samples/fileio/init.o
> >
> >
> > The -B option should have a full path not a partial one. The $prefix
> used when
> > building the BSP is missing.
> >
> > Did you use a full path? Is there an argument missing to the invocation?
> >
>
> The link provided to our wiki does not have the full path. I am not sure
> why ...
>
> >     References:
> >     [1] https://devel.rtems.org/wiki/Developer/Tracing/Trace_Buffering
> >     <https://devel.rtems.org/wiki/Developer/Tracing/Trace_Buffering>
>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180319/c5c922db/attachment-0002.html>