You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KEDR's inability to analyze several modules at once is a known problem.
There should be an open issue about it :)
Just an example where it's important: consider DRM-based GPU driver. When it's
loaded, a whole bunch of other modules is also loaded.
i915, cfbfillrect, cfbimgbit, i2c_algo_bit, cfbcopyarea, drm_kms_helper, drm,
intel_agp, intel_gtt, agpgart
Original issue reported on code.google.com by [email protected] on 19 May 2013 at 11:42
The text was updated successfully, but these errors were encountered:
I agree. The wireless networking stack is another common example where support
for multiple modules is highly desirable.
This feature has been on my TODO list for quite some time. I have already
implemented support for multi-module analysis in our data race detector,
KernelStrider, and will port that code to KEDR when I have time. It is
manageable but not that easy.
Currently, support for networking drivers in KernelStrider has the highest
priority for me. When I am done with that (no later than the end of June, I
hope), I plan to finally add support for analyzing multiple modules to KEDR.
Original issue reported on code.google.com by
[email protected]
on 19 May 2013 at 11:42The text was updated successfully, but these errors were encountered: