Re: [Discuss-gnuradio] Segmentation fault issue with gr_hier_block2_detail::connect

2013-10-01 Thread Naceur
Thank you Marcus for the reply, I just figured out where was the problem: I am TWICE instantiating an object (a shared pointer) outside an if loop and inside of it, And for the backtrace it gives me that ... in main (argc=, argv=) ... Actually I fixed the issue. Cheers -- View this me

Re: [Discuss-gnuradio] Segmentation fault issue with gr_hier_block2_detail::connect

2013-10-01 Thread Marcus Müller
Could you provide us with a backtrace (in GDB: "bt") and if possible with the code that you use to produce this error. Usually, connect does not cause segfaults, a problem arises if you a) connect a block that does not exist yet (eg. in its constructor) b) connect a block in multiple flowgraphs

Re: [Discuss-gnuradio] Segmentation fault issue with gr_hier_block2_detail::connect

2013-10-01 Thread Naceur
And when I run again sometimes it stops and throw another segfault in the same location but labeled: Program received signal SIGSEGV, Segmentation fault. 0xb7af75f3 in gr_flowgraph::check_dst_not_used(gr_endpoint const&) () from /usr/local/lib/libgnuradio-core-3.6.5.so.0.0.0 -- View this messag

[Discuss-gnuradio] Segmentation fault issue with gr_hier_block2_detail::connect

2013-10-01 Thread Naceur
Hello GNU-Radio list, I wonder why is my C++ code is thorwing a segmentation fault (core dumped), gdb outputs: Program received signal SIGSEGV, Segmentation fault. 0xb7b1b718 in gr_hier_block2_detail::connect(boost::shared_ptr, int, boost::shared_ptr, int) () from /usr/local/lib/libgnuradio-co