On 07/10/2014 12:05 AM, Orin Lincoln wrote: > I have encountered a segmentation fault issue in the > gr::bluetooth::multi_block code (which all the other gr-bluetooth blocks > use) that did not appear while running the included QA code (though I'm > not sure how reliable the test code was). I've spent the past couple > days trying to track down with GDB what exactly is going wrong, so that > I can fix it (the code looks fine to me, nothing is standing out as a > big issue). From what I've gathered so far, it appears the issue is with > "gr_vector_void_star& out", an input to multi_block::channel_samples(). > I don't have a lot of experience with debugging, so if anyone has any > suggestions about what to look for when tracking down segmentation > faults (my understanding is that > memory is being accessed which should not be accessed by the process), I > would appreciate them.
If you build GNU Radio with debug symbols and follow the instructions on http://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsDebugging, you can figure out exactly where the segfault is happening; that'll help you fix the problem. M _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
