[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Using disconnect_all() in C++
From: |
Alexandru Csete |
Subject: |
Re: [Discuss-gnuradio] Using disconnect_all() in C++ |
Date: |
Fri, 22 Feb 2013 00:57:04 +0100 |
On Fri, Feb 22, 2013 at 12:14 AM, Johnathan Corgan
<address@hidden> wrote:
> On Thu, Feb 21, 2013 at 3:08 PM, Alexandru Csete <address@hidden> 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] Using disconnect_all() in C++, Alexandru Csete, 2013/02/21
- Re: [Discuss-gnuradio] Using disconnect_all() in C++, Johnathan Corgan, 2013/02/21
- Re: [Discuss-gnuradio] Using disconnect_all() in C++, Alexandru Csete, 2013/02/21
- Re: [Discuss-gnuradio] Using disconnect_all() in C++, Johnathan Corgan, 2013/02/21
- Re: [Discuss-gnuradio] Using disconnect_all() in C++, Alexandru Csete, 2013/02/21
- Re: [Discuss-gnuradio] Using disconnect_all() in C++, Johnathan Corgan, 2013/02/21
- Re: [Discuss-gnuradio] Using disconnect_all() in C++,
Alexandru Csete <=
- Re: [Discuss-gnuradio] Using disconnect_all() in C++, Johnathan Corgan, 2013/02/21
- Re: [Discuss-gnuradio] Using disconnect_all() in C++, Johnathan Corgan, 2013/02/21