Re: [Discuss-gnuradio] Using disconnect_all() in C++
On Thu, Feb 21, 2013 at 2:36 PM, Alexandru Csete oz9...@gmail.com wrote: terminate called after throwing an instance of 'std::invalid_argument' what(): input port 0 out of range for complex_to_float(26) Aborted (core dumped) Can you get a gdb stack traceback on this? If I disconnect the blocks manually it works fine, which lead me to believe that disconnect_all() only works at top-block level? Or maybe a bug? It's very likely a bug. Johnathan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Using disconnect_all() in C++
On Thu, Feb 21, 2013 at 11:47 PM, Johnathan Corgan johnat...@corganlabs.com wrote: On Thu, Feb 21, 2013 at 2:36 PM, Alexandru Csete oz9...@gmail.com wrote: terminate called after throwing an instance of 'std::invalid_argument' what(): input port 0 out of range for complex_to_float(26) Aborted (core dumped) Can you get a gdb stack traceback on this? I can do that but I need some instructions. Do I need to build gnuradio with special flags or just the usual cmake/make? Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Using disconnect_all() in C++
On Fri, Feb 22, 2013 at 12:05 AM, Johnathan Corgan johnat...@corganlabs.com wrote: On Thu, Feb 21, 2013 at 3:02 PM, Alexandru Csete oz9...@gmail.com wrote: I can do that but I need some instructions. Do I need to build gnuradio with special flags or just the usual cmake/make? Add -DCMAKE_BUILD_TYPE=DEBUG to your usual cmake command line. This adds the symbol tables to the generated libraries, so gdb can do its thing. Ok, I'll do that; in gdb then I run strace or backtrace after it crashes? Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Using disconnect_all() in C++
On Thu, Feb 21, 2013 at 3:02 PM, Alexandru Csete oz9...@gmail.com wrote: I can do that but I need some instructions. Do I need to build gnuradio with special flags or just the usual cmake/make? Add -DCMAKE_BUILD_TYPE=DEBUG to your usual cmake command line. This adds the symbol tables to the generated libraries, so gdb can do its thing. Johnathan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Using disconnect_all() in C++
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. Johnathan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Using disconnect_all() in C++
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
Re: [Discuss-gnuradio] Using disconnect_all() in C++
On Thu, Feb 21, 2013 at 3:57 PM, Alexandru Csete oz9...@gmail.com wrote: 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. Can you confirm you are linked against libgnuradio with debugging symbols? There are no stack frames from gnuradio between #5 and #6. This may also be from running inside the QT event loop, having QT absorb the exception, then rethrowing it. So if you can get this to happen outside QT and verify the debug libraries are actually linked to, that would help. Johnathan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Using disconnect_all() in C++
On Thu, Feb 21, 2013 at 4:10 PM, Johnathan Corgan johnat...@corganlabs.comwrote: So if you can get this to happen outside QT and verify the debug libraries are actually linked to, that would help. Sorry, lower in the log it does show GR debug symbols so nevermind on that. Let's take the rest of this off list. Johnathan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
