On Fri, Feb 22, 2013 at 12:14 AM, Johnathan Corgan <johnat...@corganlabs.com> wrote: > On Thu, Feb 21, 2013 at 3:08 PM, Alexandru Csete <oz9...@gmail.com> wrote: > >> >> Ok, I'll do that; in gdb then I run strace or backtrace after it crashes? > > > $ gdb gqrx > [...] > (gdb) set args --foo --bar [if needed] > (gdb) run > [...segfault output...] > (gdb) bt > (gdb) info threads > > The output from bt and info threads should tell us exactly where it is > faulting. Actually, that's already known, its an error handler that is > throwing due to bad data, but the stack trace will tell us who was calling > it. >
I have attached the trace - I hope you can see something from it. If Qt is interfering I can try to create a simpler example. Alex
trace.log
Description: Binary data
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
