Re: [PATCH v1] Port ndbm

On Fri, Jun 21, 2019 at 1:42 PM Vaibhav Gupta wrote: > > > > On Fri, Jun 21, 2019 at 11:38 PM Gedare Bloom wrote: >> >> On Fri, Jun 21, 2019 at 11:03 AM Vaibhav Gupta >> wrote: >> > >> > >> > >> > On Fri, Jun 21, 2019, 9:46 PM Gedare Bloom wrote: >> >> >> >> On Fri, Jun 21, 2019 at 4:25 AM

Re: [PATCH v1] Port ndbm

On Fri, Jun 21, 2019 at 11:38 PM Gedare Bloom wrote: > On Fri, Jun 21, 2019 at 11:03 AM Vaibhav Gupta > wrote: > > > > > > > > On Fri, Jun 21, 2019, 9:46 PM Gedare Bloom wrote: > >> > >> On Fri, Jun 21, 2019 at 4:25 AM Vaibhav Gupta > wrote: > >> > > >> > Hello Gedare, > >> > As you

Re: [PATCH v1] Port ndbm

On Fri, Jun 21, 2019 at 11:03 AM Vaibhav Gupta wrote: > > > > On Fri, Jun 21, 2019, 9:46 PM Gedare Bloom wrote: >> >> On Fri, Jun 21, 2019 at 4:25 AM Vaibhav Gupta >> wrote: >> > >> > Hello Gedare, >> > As you suggested, I have placed nbm.cinlibc/search directory. >> > This

Re: [PATCH v1] Port ndbm

On Fri, Jun 21, 2019, 9:46 PM Gedare Bloom wrote: > On Fri, Jun 21, 2019 at 4:25 AM Vaibhav Gupta > wrote: > > > > Hello Gedare, > > As you suggested, I have placed nbm.cinlibc/search > directory. This directory contains hash.h, db_local.h, hash.c. And all > these are required by

Re: CTF example

On Fri, Jun 21, 2019 at 10:10 AM Ravindra Kumar Meena wrote: > > Hi, > > Thanks for sharing the example. > > I managed to store the RTEMs event stream in a file. I have also written the > metada for the same but babeltrace is not able to read CTF because metadata > is not compatible with it. >

Re: [PATCH v1] Port ndbm

On Fri, Jun 21, 2019 at 4:25 AM Vaibhav Gupta wrote: > > Hello Gedare, > As you suggested, I have placed nbm.cinlibc/search directory. > This directory contains hash.h, db_local.h, hash.c. And all these are > required by ndbm. > . > Here newlib got successfully compiled and It was

Re: CTF example

Hi, Thanks for sharing the example. I managed to store the RTEMs event stream in a file. I have also written the metada for the same but babeltrace is not able to read CTF because metadata is not compatible with it. Do you have any example or approach to make metadata compatible with events?

Re: Add newlib patch to RTEMS RSB

On Fri, Jun 21, 2019, 9:19 PM Gedare Bloom wrote: > On Fri, Jun 21, 2019 at 2:37 AM Vaibhav Gupta > wrote: > > > > Hello, > > I figured it out. > > . > > Below is the output given by shell > > .. > > .. > > .. > > config: tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg > > warning:

Re: [PATCH] Write event stream in file

On Fri, Jun 21, 2019 at 8:51 AM Ravindra Kumar Meena wrote: >> >> >> I tried to parse the event stream file and metadata file through >> >> babeltrace gives the following error: >> >> >> >> [error] Invalid magic number 0x30302E30 at packet 0 (file offset 0). >> >> [error] Stream index creation

Re: Add newlib patch to RTEMS RSB

On Fri, Jun 21, 2019 at 2:37 AM Vaibhav Gupta wrote: > > Hello, > I figured it out. > . > Below is the output given by shell > .. > .. > .. > config: tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg > warning: rtems-gcc-7.4.0-newlib-1d35a003f.cfg:29: invalid format: '%setup > patch newlib

Re: GSoC Project | Basic Support for Trace Compass

*21 June work summary:* I have managed to store event streams in the disk. Tried to parse metadata and event stream file through babeltrace but it showing error as of now because the metadata file is not compatible with it. Raised a query on babletrace list asking about the same. It needs bit of

Re: [PATCH] Write event stream in file

> > > I tried to parse the event stream file and metadata file through > > babeltrace gives the following error: > > > > [error] Invalid magic number 0x30302E30 at packet 0 (file offset 0). > > [error] Stream index creation error. > > [error] Open file stream error. > > [warning] [Context] Cannot

Re: [PATCH] Write event stream in file

> > > I was able to store the event stream in file. I have sent the patch for > > the same. It has only one warning that I have to discuss with you. > > > > ../misc/record/record-main.c:172:14: warning: ‘ns’ may be used > > uninitialized in this function [-Wmaybe-uninitialized] > >

Re: Add newlib patch to RTEMS RSB

On Fri, Jun 21, 2019, 7:19 PM Joel Sherrill wrote: > > > On Fri, Jun 21, 2019 at 3:37 AM Vaibhav Gupta > wrote: > >> Hello, >> I figured it out. >> . >> Below is the output given by shell >> .. >> .. >> .. >> config: tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg >> warning:

Re: Add newlib patch to RTEMS RSB

On Fri, Jun 21, 2019 at 3:37 AM Vaibhav Gupta wrote: > Hello, > I figured it out. > . > Below is the output given by shell > .. > .. > .. > config: tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg > warning: rtems-gcc-7.4.0-newlib-1d35a003f.cfg:29: invalid format: '%setup > patch newlib

Re: [PATCH] Write event stream in file

On 21/06/2019 14:28, Sebastian Huber wrote: On 21/06/2019 14:16, Ravindra Kumar Meena wrote: Hi, I tried to parse the event stream file and metadata file through babeltrace gives the following error: [error] Invalid magic number 0x30302E30 at packet 0 (file offset 0). [error] Stream index

Re: [PATCH] Write event stream in file

On 21/06/2019 14:16, Ravindra Kumar Meena wrote: Hi, I tried to parse the event stream file and metadata file through babeltrace gives the following error: [error] Invalid magic number 0x30302E30 at packet 0 (file offset 0). [error] Stream index creation error. [error] Open file stream

Re: [PATCH] Write event stream in file

On 21/06/2019 13:20, Ravindra Kumar Meena wrote: Hi, I was able to store the event stream in file. I have sent the patch for the same. It has only one warning that I have to discuss with you. ../misc/record/record-main.c:172:14: warning: ‘ns’ may be used uninitialized in this function

Re: [PATCH] Write event stream in file

Hi, I tried to parse the event stream file and metadata file through babeltrace gives the following error: [error] Invalid magic number 0x30302E30 at packet 0 (file offset 0). [error] Stream index creation error. [error] Open file stream error. [warning] [Context] Cannot open_trace of format ctf

Re: [PATCH] Write event stream in file

Hi, I was able to store the event stream in file. I have sent the patch for the same. It has only one warning that I have to discuss with you. ../misc/record/record-main.c:172:14: warning: ‘ns’ may be used uninitialized in this function [-Wmaybe-uninitialized] ctf_item.ns=ns; ^

[PATCH v2] Write event stream in file

--- misc/record/record-main.c | 30 ++ 1 file changed, 14 insertions(+), 16 deletions(-) diff --git a/misc/record/record-main.c b/misc/record/record-main.c index eccf291..9e9eaa3 100644 --- a/misc/record/record-main.c +++ b/misc/record/record-main.c @@ -83,6 +83,7 @@

Re: [PATCH v1] Port ndbm

Hello Gedare, As you suggested, I have placed nbm.cinlibc/search directory. This directory contains hash.h, db_local.h, hash.c. And all these are required by ndbm. . Here newlib got successfully compiled and It was generating function symbols. . After that when i added the patch to

Re: [PATCH] Write event stream in file

On 21/06/2019 10:33, Ravindra Kumar Meena wrote: The static void print_item( FILE *f, const client_item *item ) gets already a file, please use it. The file is currently stdout.  This should be changed to an event stream file.  Add the file pointer to client_context

Re: [PATCH] Write event stream in file

> > > The > > static void print_item( FILE *f, const client_item *item ) > > gets already a file, please use it. > > The file is currently stdout. This should be changed to an event stream > file. Add the file pointer to client_context and open the file in main(). > > Are you suggesting to

Re: [PATCH] Write event stream in file

On 21/06/2019 08:57, Ravindra Kumar Meena wrote: >     seconds = (uint32_t) ( item->ns / 10 ); >     nanoseconds = (uint32_t) ( item->ns % 10 ); > +    ns=nanoseconds; Why not move the nanoseconds variable into the upper block? Okay >     fprintf( f,

Re: [PATCH] Write event stream in file

> > seconds = (uint32_t) ( item->ns / 10 ); > > nanoseconds = (uint32_t) ( item->ns % 10 ); > > +ns=nanoseconds; > > Why not move the nanoseconds variable into the upper block? > Okay > > > fprintf( f, "%" PRIu32 ".%09" PRIu32 ":", seconds, nanoseconds ); > > }