>I am not sure you can do this without providing your own babeltrace
source component in a separate plugin to what is already available. If
the trace is not converted to a useful CTF format.
Yes. The blog post is merely to demonstrate how to use babeltrace. We will
not be dealing with text trace i
On Tue, 2018-07-03 at 07:50 +0530, Vidushi Vashishth wrote:
> > 3. Clearly document your modifications in separate commit messages.
>
> > 4. Add a Makefile to build it automatically.
>
> I will push commits to a fork of the rtems. Have given a link to the
> repository in the readme.md of the Trac
On 03/07/18 14:50, Vidushi Vashishth wrote:
Hi!
> Ok, thanks, but why did you remove the RTEMS application? This is
the first step. The repository should contain a sample application
with a Makefile (or waf or whatever, but no manual steps) to generate
a sample trace raw data.
I was testing
On 03/07/18 04:20, Vidushi Vashishth wrote:
> 3. Clearly document your modifications in separate commit messages.
> 4. Add a Makefile to build it automatically.
I will push commits to a fork of the rtems. Have given a link to the
repository in the readme.md of the Tracing repo. Will that be ok
> 3. Clearly document your modifications in separate commit messages.
> 4. Add a Makefile to build it automatically.
I will push commits to a fork of the rtems. Have given a link to the
repository in the readme.md of the Tracing repo. Will that be okay?
> 6. Document the steps involved in the tr
On Mon, Jul 2, 2018 at 1:27 AM, Sebastian Huber
wrote:
> Hello Vidushi,
>
> On 29/06/18 09:44, Vidushi Vashishth wrote:
>>
>>
>> >Could you please create a self-contained repository which
>> contains
>>
>> >* a README
>>
>> >* a simple RTEMS application which runs on a simu
Hello Vidushi,
On 29/06/18 09:44, Vidushi Vashishth wrote:
>Could you please create a self-contained repository which contains
>* a README
>* a simple RTEMS application which runs on a simulator BSP
>* the stuff that makes it possible to view the trace output
Hi!
https://github.com/VidushiVashishth/Tracing
This is the required repository. I read up the POSIX API documentation to
understand that nothing of the like of system( ) would work on rtems since
its a single process os.
The main_rtrace.c in the given repository currently consists of this wrong
On 29 Jun 2018, at 5:44 pm, Vidushi Vashishth wrote:
>>> >Could you please create a self-contained repository which contains
>>>
>>> >* a README
>>>
>>> >* a simple RTEMS application which runs on a simulator BSP
>>>
>>> >* the stuff that makes it possible to view the trace output (it is not
>
> >Could you please create a self-contained repository which contains
>>
>> >* a README
>>
>> >* a simple RTEMS application which runs on a simulator BSP
>>
>> >* the stuff that makes it possible to view the trace output (it is not a
>> problem if it doesn't work, but all pieces should be include
On 28/06/18 19:41, Vidushi Vashishth wrote:
>Could you please create a self-contained repository which contains
>* a README
>* a simple RTEMS application which runs on a simulator BSP
>* the stuff that makes it possible to view the trace output (it is
not a problem if it doesn't work, but all
>Could you please create a self-contained repository which contains
>* a README
>* a simple RTEMS application which runs on a simulator BSP
>* the stuff that makes it possible to view the trace output (it is not a
problem if it doesn't work, but all pieces should be included)
>The repository sh
On 28/06/18 07:42, Vidushi Vashishth wrote:
>which use case does this address? What is the connection to an RTEMS
application?
This converts the trace buffering of the fileio sample testcase output
to CTF. This pertains to the function tracing testcase. The CTF stream
generated records the ent
>which use case does this address? What is the connection to an RTEMS
application?
This converts the trace buffering of the fileio sample testcase output to
CTF. This pertains to the function tracing testcase. The CTF stream
generated records the entry and exit of the calloc, malloc, realloc and
fr
>Run on what? RTEMS?
yes.
>Are there any RTEMS repos with your work?
I havent pushed my code since it is throwing errors. Should I push it
nonetheless for you to see? Or create another repo?
>RTEMS does not support `system()`.
Does RTEMS support fdopen or popen? I am trying to execute the babeltr
Hello,
On 28/06/18 05:48, Vidushi Vashishth wrote:
Hi!
Sorry for the delay. I had been trying to make the code run.
https://github.com/VidushiVashishth/babeltrace/tree/master/Demo
This is a demonstration of the how to use babeltrace to convert rtems
traces.
which use case does this address?
On 28/06/2018 13:48, Vidushi Vashishth wrote:
>
> Sorry for the delay. I had been trying to make the code run.
Run on what? RTEMS?
> https://github.com/VidushiVashishth/babeltrace/tree/master/Demo
Are there any RTEMS repos with your work?
> This is a demonstration of the how to use babeltrace
Hi!
Sorry for the delay. I had been trying to make the code run.
https://github.com/VidushiVashishth/babeltrace/tree/master/Demo
This is a demonstration of the how to use babeltrace to convert rtems
traces. I have integrated the program.c code in the rtems main_rtrace.c
file. This is throwing some
Hello Vidushi,
On 22/06/18 03:16, Vidushi Vashishth wrote:
Progress so far:
- Still working on adding rtrace shell capability to convert RTEMS
traces into CTF. There has been progress which I will push to
(https://github.com/VidushiVashishth/rtems) by end of today.
I don't see an update in
Hi!
I have updated the weekly status of my work on the GSoC tracking page. Here
is a summary of it:
Progress so far:
- Still working on adding rtrace shell capability to convert RTEMS traces
into CTF. There has been progress which I will push to (
https://github.com/VidushiVashishth/rtems) by en
Hello Vidushi,
On 12/06/18 14:22, Vidushi Vashishth wrote:
>in case you receive comments for your patches the highest priority should be to fix the problems with the
patches and send the next revision of the patch to the list, e.g.
fixing trivial things like the line ?>length should be done in
Hi!
>in case you receive comments for your patches the highest priority should
be to fix the problems with the patches and send the next revision of the
patch to the list, e.g. fixing trivial things like the line ?>length should
be done in a couple of minutes. If you think a comment is invalid or
Hello Vidushi,
in case you receive comments for your patches the highest priority
should be to fix the problems with the patches and send the next
revision of the patch to the list, e.g. fixing trivial things like the
line length should be done in a couple of minutes. If you think a
comment i
Hi!
Updating the status on the tracing project. I am working on a ctftrace
function in the main_rtrace.c file in rtems source code which will use the
libbabeltrace C API to convert the trace buffers and print the final CTF
onto the console. I am using a static metadata specific to the fileio
sampl
Hi!
Just updating that I have sent a patch which fixes the trace buffer
generation. I am now able to generate trace buffers for the fileio sample
testcase. I will begin work on CTF conversion now.
Thanks,
Vidushi
On Tue, May 29, 2018 at 1:00 PM, Vidushi Vashishth
wrote:
> Hey Sebastian!
>
> Ye
Hey Sebastian!
Yes I have been working on the trace linker the past week. It is outdated
and needs improvements. A lot of my work depends on me fixing the trace
linker. I had informed about this last week during the meeting. I thought I
would update you as soon as I make progress. Nevertheless the
Hello Vidushi,
I though you agreed to send a regular status report on Monday? Do you
still work on the project?
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@emb
27 matches
Mail list logo