Emulated Collection Proxy need to always use the VectorLooper for the StreamerInfoActions#9750
Conversation
|
Starting build on |
eguiraud
left a comment
There was a problem hiding this comment.
I'll have to trust you that the new logic is better than the old 😄
Maybe the commit message could be more verbose about what was wrong before and how this patch fixes it.
Also, should we have a test for the case this fixes?
Fair enough, I will expand.
Yes :) Can you add the test you case you had? |
…erInfoActions This fixes root-project#9136. Without this commit, SelectLooper would select the 'GenericLooper' in the case of an emulated proxy for STL collection with (in the name) a custom allocator. However the GenericLooper only usable for collection with a compiled collection proxy. In particular, GenericLooper is calling the 'Next' function which is not defined for vector ... and emulated collection. Using it lead to an assert complaining (right fully so) that an 'undefined' function is being called.
dfcf963 to
68d37bc
Compare
|
Starting build on |
That needed valgrind to detect anything. @pcanal can we use |
|
No valgrind necessary. The failure is a call to |
|
OK, I don't think we should wait for someone to add a test (unless it's you @pcanal ). Please merge this especially into v6-26... |
This fixes #9136.