hi,
thanks for that,
I've done severals tests.
One with bisect and it finds with its dichotomy method that commit
af05802ced7516d008f54b97d7a2a628e8b84a64 is the last working version with
pix_opencv between 0.93 tag and master
You can find the bisect log in attachment.
the other test i made is to start from master and go back through the
rev-list to 0.93 commit by commit until i found a working version
the first one I found is : 4b1ec61b29ce82e5b20eb67bc7900cf6dd54aadb
this test was made with a script (see attachment)
moreover i can go forward from this working point until commit
5b62940b3a260d814c3eb4f9791e13c9c0539ec5 and make pix_opencv working
but when i'm going in the reverse way it crashes and the first working
commit i found is af05802ced7516d008f54b97d7a2a628e8b84a64 (the same as
bisect found)
but i didn't test all...
git diff says me a lot of things but i can't understand where the issue
with pix_opencv is
i hope thoses informations are enough to quickly fix the issue cause it
freaks me out !
cheers
antoine
--
do it yourself
http://antoine.villeret.free.fr
http://drii.ensad.fr
--
Google lit ce mail...
si vous refusez cela, utilisez l'adresse antoine.villeret [at] free.fr pour
me contacter
2012/2/14 IOhannes m zmölnig
zmoelnig@iem.at
> On 02/13/12 22:30, Antoine Villeret wrote:
>
>> hi,
>>
>> pix_opencv still crashes with GEM from git after 0.93.3 tag
>> two weeks later and some time spend to figure out which commit broke the
>> things i need help
>> i can't figure out what happen in the gem code since the 11th of
>> november 2011 that can crash pix_opencv
>> moreover i don't know how to investigate through all the commits to
>> identify the cause easily
>>
>> any advice would be great...
>>
>>
> "git bisect" is a great tool for finding a regressions that appeared
> "somewhen" using binary search.
> since it is a crash, you could even write a simple test, that fully
> automates the bughunt. (note: the crash makes it simpler because of Pd, not
> because of 'git bisect')
>
> fgmar
> IOhannes
>
> ______________________________**_________________
> GEM-dev mailing list
> GEM-dev@iem.at
>
http://lists.puredata.info/**listinfo/gem-devhttp://lists.puredata.info/listinfo/gem-dev
>
