Name

bfbin2sqlite3 - convert Byfl output to a SQLite3 database file

Synopsis

bfbin2sqlite3 [--output=filename.db] [--live-data] filename.byfl

bfbin2sqlite3 --help

Description

By default, applications instrumented with Byfl write measurement data to a binary .byfl file. bfbin2sqlite3 converts such files to SQLite3 database files. These can be loaded directly into the sqlite3 command-line database tool or converted into other database formats.

Options

bfbin2sqlite3 accepts the following command-line options:

• -h, --help

  Output a brief usage message.

• -o filename.db, --output=filename.db

  Specify the name of the output file. If this option is not specified, the name of the database file will be the same as that of the input file but with .byfl replaced with .db. (If the file name does not end in .byfl then .db will be appended to the file name.)

• -l, --live-data

  Indicate that the input file is being generated concurrently with bfbin2sqlite3's execution. When --live-data is specified, a premature end of file causes bfbin2sqlite3 to wait for more data to arrive instead of immediately producing an error message and aborting.

In addition, the name of a binary .byfl input file must be provided on the command line.

Examples

The simplest usage is just

$ bfbin2sqlite3 myprog.byfl

which produces myprog.db.

If the .byfl file is expected to be used only to produce the SQLite3 database and then deleted, one can save time and disk space by writing Byfl binary output to a named pipe and running bfbin2sqlite3 on that named pipe:

$ mkfifo myprog.pipe
$ bfbin2sqlite3 myprog.pipe myprog.db &
$ env BF_BINOUT=myprog.pipe ./myprog
$ rm myprog.pipe

See also

sqlite3(1), bfbin2cgrind(1), bfbin2csv(1), bfbin2hdf5(1), bfbin2hpctk(1), bfbin2xmlss(1), bf-clang(1), bf-clang++(1), bf-flang(1), the Byfl home page, the SQLite home page

Author

Scott Pakin, [email protected]