On 03/15/2012 02:26 PM, Stefan Ott wrote: > On Thu, Mar 15, 2012 at 18:02, Stefan Ott <o...@iam.unibe.ch> wrote: >> >>> Finally, there are docs on the web for working out where in the code the >>> oops really occurs. Can you try working through that procedure and see >>> if it happens in the driver, or elsewhere. >> >> Ok, I'll see whether I can find it and report back once I have more >> information. > > So far, what I've found through the magic of strace and printf is that > the offending call seems to be the USRP_E_WRITE_CTL32 ioctl that > happens as a consequence of poke32 (in e100_ctrl.cpp) when called from > e100_ctrl_impl. > > That's still with (vanilla) kernel 3.1.10 though.
Can you look carefully at what data is being passed to the driver? We may need to range check the data before we use it in the driver. Philip _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
