Re: latrace 0.5.10
by Jiri Olsa
hi,
thanks for the changes, I have some comments/questions..
wbr,
jirka
On Sun, Feb 13, 2011 at 10:05 PM, Sebastian Pipping <sping(a)gentoo.org> wrote:
> Hello Jiri,
>
>
> I came across latrace and played with a Gentoo ebuild for it, current
> result at [1]. On the way I discovered a few minor issues with the
> release of 0.5.10:
>
> - Compile flags are not respected everywhere. Please consider
> application of attached patch.
I'm ok with CFLAGS being used for linking, but I'm not sure
whats the benefit with LDFLAGS in compile.. I looked over few
projects (flex/strace/utliss-linux-ng) and none seems to be using this.
Could you please specify the reason?
>
> - A configure script is required, but the script itself is not shipped.
> Please adjust your packaging scripts accordingly.
You can get the configure script by running 'autoconf', but I guess you need it
in the package without running anything right?
Is it gento requirement?
>
> - Packaging for Debain is shipped twice:
> - debian/
> - package/debian/
yep, thats confusing :) looks like ./debian/changelog is more recent
Akos, can I move it to the ./package/ ?
13 years, 2 months
- 4
- 5
new latrace code - global_sym/cofig-file/error-simulation
by Jiri Olsa
hi,
I have some load of new latrace code to commit, so I thought I'd ask
you for review/ideas.. whatever is helpful, so I wont be the only one
to blame ;)
The reason for all the new code was the idea of error simulation via latrace.
Imagine you could specify what will certain function return and watch how
the application behave afterwards. For example having malloc to return NULL,
and simulate the allocation failure.
I started implementing this idea and it split into 3 parts:
global symbol place
- I needed global symbol place keeping all the info -
arguments/errors, so it'd be searched
just once
config file
- for error simulation I need to have configuration file, so I could specify
the details of simulation. That was the reason I added config file and added
support for some of the command line options.
error simulation
- the configuration is done in 2 parts.
First you specify in the latrace config file:
what you want to simulate
what functions to use for this
how to run the program,
how many times
when to trigger the error..
Second there's configuration record for each function you want to use.
You specify
what return codes to use so far..
thats basicaly it so far.. :)
The current state is:
global_symbol
- already in master branch
config file supprot
- in config branch
- should be complete, dont have any pending work for now
error simulation
- in error branch
- it is able to tun and simulate the error sequencionaly.. each run,
the error is done in the next function call
- it's very basic, it lacks the implementation of many configuration options
- needs to watch and store traced program output (0/1/2 desc.)
I plan to put config file support into master branch soon and finish the error
simulation into some user usable state.. than I'd like to spin out 0.6 release..
any feedback is welcome :)
thanks,
jirka
13 years, 2 months
- 1
- 0
- ← Newer
- 1
- Older →