eellak/build-recorder

Issues

• First release tarball isn't updated after #213

  #220 opened 7 months ago by fvalasiad
  0

• `build-recorder` executable placed under `src/` instead of toplevel.

  #216 opened a year ago by fvalasiad
  2

• xxd -n option

  #214 opened a year ago by fvalasiad
  8

• Compare with tracecode

  #154 opened 2 years ago by zvr
  3

• `time` `awk` and `wget/curl` unnecessarily required to build `build-recorder`

  #205 opened a year ago by fvalasiad
  2

• Failure building `build-recorder` with automated build & packaging `xbps-src` tool.

  #209 opened a year ago by fvalasiad
  2

• Cannot build from first release

  #212 opened a year ago by fvalasiad
  0

• configure should check everything

  #177 opened a year ago by zvr
  1

• possible useful background information

  #210 opened a year ago by armijnhemel
  1

• Rebuilding stuff after SOME changes.

  #204 opened a year ago by fvalasiad
  0

• Output has to use the schema

  #197 opened a year ago by zvr
  2

• Standardized benchmarking

  #186 opened a year ago by zvr
  16

• Invalid use of `AC_CHECK_PROGS`

  #199 opened a year ago by fvalasiad
  4

• `time(1)` is confused with the shell's `time` built-in keyword.

  #198 opened a year ago by fvalasiad
  0

• Automated tests

  #142 opened 2 years ago by fvalasiad
  1

• Implement tests

  #190 opened a year ago by zvr
  1

• Tests makefile integration

  #185 opened a year ago by zvr
  2

• `build-recorder` build failure.

  #194 opened a year ago by fvalasiad
  2

• Provide schema for generated RDF

  #166 opened a year ago by zvr
  0

• Missing man page

  #184 opened a year ago by zvr
  1

• Extended functionality for build systems that interact with remote repositories.

  #189 opened a year ago by fvalasiad
  0

• Document build/install process

  #165 opened a year ago by zvr
  1

• `PROCESS_INFO` structure issues, missing free on PROCESS_INFO::entry_info in case of syscall failure

  #181 opened 2 years ago by fvalasiad
  0

• `rename(2)` entry handler is invalid

  #179 opened 2 years ago by fvalasiad
  1

• `build_recorder(3)` kills parallelism

  #151 opened 2 years ago by fvalasiad
  0

• Building `build_recorder` on a raspberry pi

  #149 opened 2 years ago by fvalasiad
  1

• Portability

  #175 opened 2 years ago by fvalasiad
  0

• Valgrind Errors

  #172 opened 2 years ago by KonstantinosZach
  0

• FreeBSD support

  #162 opened 2 years ago by fvalasiad
  0

• mmap error with maven

  #167 opened 2 years ago by IordanisSap
  7

• crash when recording complex build (gcc)

  #170 opened 2 years ago by zvr
  0

• Document contributing guidelines

  #163 opened 2 years ago by zvr
  0

• Use consistent naming

  #164 opened 2 years ago by zvr
  0

• Support multiple hash algorithms (not SHA-1)

  #153 opened 2 years ago by timretout
  4

• [DOCS] Doxygen Support

  #159 opened 2 years ago by resyfer
  5

• Consistency on error checking

  #156 opened 2 years ago by fvalasiad
  0

• Seg fault on Improper Use

  #155 opened 2 years ago by resyfer
  2

• `finfo` data structure

  #150 opened 2 years ago by fvalasiad
  1

• Regarding finfo & pinfo data structures

  #122 opened 2 years ago by fvalasiad
  0

• Regarding performance

  #131 opened 2 years ago by fvalasiad
  6

• [BUG] segfault at `find_finfo(3)`

  #123 opened 2 years ago by fvalasiad
  3

• Outdated doc

  #127 opened 2 years ago by fvalasiad
  0

• Regarding `sync(2)`, `syncfs(2)` `fsync(2)`,`fdatasync(2)`

  #136 opened 2 years ago by fvalasiad
  0

• First executable file not recorded

  #126 opened 2 years ago by zvr
  1

• executables aren't recorded as files

  #119 opened 2 years ago by fvalasiad
  0

• Outname field of `PROCESS_INFO` and `FILE_INFO` are redundant.

  #107 opened 2 years ago by fvalasiad
  1

• `clone(2)`, `fork(2)`, `vfork(2)` sometimes run before post-attach `SIGSTOP`

  #118 opened 2 years ago by fvalasiad
  0

• How do we handle termination?

  #116 opened 2 years ago by fvalasiad
  0

• Allowing the user to perform tracee-only enviroment and user changes

  #113 opened 2 years ago by fvalasiad
  0

• Relative and Absolute path regarding `rename(2)`

  #110 opened 2 years ago by fvalasiad
  0