Re: [Discuss-gnuradio] Segmentation fault (core dumped)

Is it this issue: http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#My-application-segfaults-immediately-It-used-to-work-and-I-didnt-change-it-What-the ? M On 01/09/2016 02:26 AM, shortwaved...@comcast.net wrote: > Hello! > > I unfortunately ended up reloading gnuradio and now I'm getting

[Discuss-gnuradio] Segmentation fault (core dumped)

Hello! I unfortunately ended up reloading gnuradio and now I'm getting a "Segmentation fault (core dumped)" My system is Ubuntu 14.04LTS/64bit machine and I originally used pybombs before I messed things up and did an uninstall gnuradio with Synaptic. I then reloaded using the install guide

Re: [Discuss-gnuradio] Segmentation fault

On 24.11.2015 16:55, Tom Rondeau wrote: > Marcus is usually quite to point out this link. Surprised he hasn't so > far :p You're right, I'm constantly surprising myself, too :P Also, in your case, Ekko, I would also have pointed you to the more specifically GDB-oriented tutorial, http://gnuradio.

Re: [Discuss-gnuradio] Segmentation fault

Hi Ekko, really, use GDB, not Pdb. Just "run" your program, than "backtrace"; stepping through it is really really tedious, and isn't really extremely helpful unless you know intimately where to look. As Tom mentioned, the debugging (and the GDB) tutorial will be helpful. Best regards, Marcus O

Re: [Discuss-gnuradio] Segmentation fault

On Tue, Nov 24, 2015 at 10:47 AM, West, Nathan wrote: > We're short on information to actually determine what's wrong here. It > looks like you're still using pdb, but I see different output/problem areas > from your screenshots. The first one looks like it crashed in tb.start, > and the second

Re: [Discuss-gnuradio] Segmentation fault

We're short on information to actually determine what's wrong here. It looks like you're still using pdb, but I see different output/problem areas from your screenshots. The first one looks like it crashed in tb.start, and the second one looks like it crashed just creating the channel model block.

Re: [Discuss-gnuradio] Segmentation fault

hi marcus i use the gdb as you said,the i debug the python file again run the fie step by step i found that the there is some problem with ‘channel model’,just like ​ you can see that self.channels_channel_model_0 = channels.channel_model( function is init the channel model block and the noise_vol

Re: [Discuss-gnuradio] Segmentation fault

Hi Chai, you're on the right track! Now, the segfault probably does not happen in "python-land", so pdb might not be the right tool. Try with gdb: gdb --args python debug_qpsk.py run program crashes backtrace Best regards, Marcus On 23.11.2015 15:01, chai E wrote: > > ​hello all > >

[Discuss-gnuradio] Segmentation fault

​hello all i followed the http://gnuradio.org/doc/doxygen/classgr_1_1digital_1_1diff__decoder__bb.html and write the same grc on e310, when i run it ,i got no GUI show , then i run the python file generated by this grc in command window, ./debug_qpsk.py i got a output message Using Volk machine

Re: [Discuss-gnuradio] Segmentation fault due to thread unsafety?

Hi Jeroen, oh, ok, then I misunderstood, sorry :) Have you been able to track down the exact place where the segfault happens? Maybe the GDB tutorial might not be the worst start: https://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsGDB You might want to set breakpoints at the position w

Re: [Discuss-gnuradio] Segmentation fault due to thread unsafety?

Hi Marcus, Thanks for your extensive reply. From your reply I am not sure if you understood that I am not doning anything graphical in work(). In very raw pigeon code this is what I have: class my_block_class : sync_block { public: vector plot_x_data, plot_y_data; work() {

Re: [Discuss-gnuradio] Segmentation fault due to thread unsafety?

Hi Jeroen, > > I suspect that a solution is that I drag all plotting into my own > block, and that also calling the plot_all() function must be done from > within the work() function (say every 100 ms). I'd say quite the opposite is true! So the point is that GUIs need to have their own loops to

[Discuss-gnuradio] Segmentation fault due to thread unsafety?

Hi all, I suspect I'm having problems with different threads which gives me a segmentation fault. Hopefully someone with knowledge on how this works with GNU radio can give me a hint for a solution. What I did is as follows (C++ implementation code is quite long, so I hope the following sket

[Discuss-gnuradio] Segmentation fault executing gnuradio-companion

Greetings GnuRadio community For a week now i am trying to install gnuradio on Ubuntu 14.04. I use the command to fetch the script wget http://www.sbrac.org/files/build-gnuradio && chmod a+x ./build-gnuradio & ./build-gnuradioand after 5 (!!) hours it finishes succesfully. After that i set

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

Sorry that I forgot to run "bt" yesterday. Here is the output of bt. = manu@radio1:narrowband$ gdb python GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 o

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

Also hoping that it would solve the issue, I rebuilt GNU Radio from todays pull. But that didn't help. manu@radio1:narrowband$ gnuradio-config-info -v v3.7.2.1-251-g67882eec On Thu, Feb 27, 2014 at 12:26 AM, Manu T S wrote: > > Thanks for the help. Here is the output. > >

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

Thanks for the help. Here is the output. manu@radio1:narrowband$ gdb python GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

Hi, Thanks for the responses. Output to "lscpu", "cat /proc/cpuinfor", "gcc -v", "python" can be found in the link below: http://home.iitb.ac.in/~manu.ts/cpu-info I am still figuring out how to get the backtrace. On Wed, Feb 26, 2014 at 11:26 PM, West, Nathan wrote: > On Wednesday, February

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

> On Wed, Feb 26, 2014 at 11:26 PM, West, Nathan > wrote: >> >> On Wednesday, February 26, 2014, Tom Rondeau wrote: >>> >>> On Wed, Feb 26, 2014 at 12:01 PM, Manu T S wrote: >>> > Hello Everyone, >>> > >>> > Not sure if this is already discussed here. >>> > >>> > I am facing segmentation fault w

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

On Wednesday, February 26, 2014, Tom Rondeau wrote: > On Wed, Feb 26, 2014 at 12:01 PM, Manu T S > > > wrote: > > Hello Everyone, > > > > Not sure if this is already discussed here. > > > > I am facing segmentation fault when running benchmark_rx in narrowband > > examples. It seems like those e

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

On Wed, Feb 26, 2014 at 12:01 PM, Manu T S wrote: > Hello Everyone, > > Not sure if this is already discussed here. > > I am facing segmentation fault when running benchmark_rx in narrowband > examples. It seems like those example used to work fine before, but now they > are having these issues.

[Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

Hello Everyone, Not sure if this is already discussed here. I am facing segmentation fault when running benchmark_rx in narrowband examples. It seems like those example used to work fine before, but now they are having these issues. on the receiver side === manu@

Re: [Discuss-gnuradio] segmentation fault in qa_constellation_receiver_test

On Fri, Feb 21, 2014 at 10:12 PM, Kelly Boswell wrote: > I'm encountering the same problem on maint. And I did remember to rebuild. > I removed the build directory, recreated it, and started over with cmake > just to be sure. It's the same stack trace. Yeah, false alarm on volk_malloc. Turns ou

Re: [Discuss-gnuradio] segmentation fault in qa_constellation_receiver_test

I'm encountering the same problem on maint. And I did remember to rebuild. I removed the build directory, recreated it, and started over with cmake just to be sure. It's the same stack trace. On Fri, Feb 21, 2014 at 7:54 PM, West, Nathan wrote: > If you just want to get back to a system that p

Re: [Discuss-gnuradio] segmentation fault in qa_constellation_receiver_test

If you just want to get back to a system that passes QA you should just be able to build off of maint. On Fri, Feb 21, 2014 at 6:05 PM, Kelly Boswell wrote: > I removed the implementation of volk_malloc that uses posix_menacing by > commenting everything from the #if to #else and the final #endif

Re: [Discuss-gnuradio] segmentation fault in qa_constellation_receiver_test

I removed the implementation of volk_malloc that uses posix_menacing by commenting everything from the #if to #else and the final #endif but the segmentation fault remains. I noticed it's being called in a few other files as well. Do I need to remove those, too? Thanks in advance. On Feb 21, 2014 1

Re: [Discuss-gnuradio] segmentation fault in qa_constellation_receiver_test

Thank you, Tom. I'll try that after I'm off of work tonight. And thank you for the great ideas, Nathan. On Fri, Feb 21, 2014 at 2:39 AM, West, Nathan wrote: > On Thu, Feb 20, 2014 at 11:25 PM, Kelly Boswell wrote: >> After the make test failed for this module, I decided to poke around to see >> i

Re: [Discuss-gnuradio] segmentation fault in qa_constellation_receiver_test

On Fri, Feb 21, 2014 at 2:39 AM, West, Nathan wrote: > On Thu, Feb 20, 2014 at 11:25 PM, Kelly Boswell wrote: >> After the make test failed for this module, I decided to poke around to see >> if there is an easy fix. I made a script that simply executes the test over >> and over until it seg faul

Re: [Discuss-gnuradio] segmentation fault in qa_constellation_receiver_test

On Thu, Feb 20, 2014 at 11:25 PM, Kelly Boswell wrote: > After the make test failed for this module, I decided to poke around to see > if there is an easy fix. I made a script that simply executes the test over > and over until it seg faults and exits after the core file is created. > > x@

[Discuss-gnuradio] segmentation fault in qa_constellation_receiver_test

After the make test failed for this module, I decided to poke around to see if there is an easy fix. I made a script that simply executes the test over and over until it seg faults and exits after the core file is created. x@:~/src/gnuradio/build/gr-digital/python/digital$ ./runtests.sh Us

Re: [Discuss-gnuradio] Segmentation fault (core dumped)

On Wed, Feb 5, 2014 at 8:36 AM, raf raf wrote: > Hello All, > > I have a Segmentation fault (core dumped), when i run digital_bert_rx.py > and digital_bert_tx.py. > > ./digital_bert_rx.py -f 2460M --rx-gain=30 --args="addr=192.168.10.2" > > ./digital_bert_tx.py -f 2460M --tx-gain=30 --args="addr=

[Discuss-gnuradio] Segmentation fault (core dumped)

Hello All, I have a Segmentation fault (core dumped), when i run digital_bert_rx.py and digital_bert_tx.py. ./digital_bert_rx.py -f 2460M --rx-gain=30 --args="addr=192.168.10.2" ./digital_bert_tx.py -f 2460M --tx-gain=30 --args="addr=192.168.10.3" --amplitude=0.2 When I run for a sevral times

[Discuss-gnuradio] Segmentation fault in when using gnuradio resampler block in c++ flowgraph

Hi all, I want to connect the rational resampler to the block called "state machine". Whenever I invoke the rational resampler I get an "SEGMENTATION FAUL" error. I use an C++ flowgraph. Header file: gr::top_block_sptr top_block; // Included hier_block2.h gr::filter::rational_resampler_base_ccf

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

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

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

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

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

Re: [Discuss-gnuradio] Segmentation fault using qt gui sink

Hi Jonathan, I got no meaningful backtrace. That is all I got: Program received signal SIGSEGV, Segmentation fault. 0x00c1 in ?? () (gdb) bt #0 0x00c1 in ?? () #1 0x7fc0ce119fcc in ?? () #2 0x02849c10 in ?? () #3 0x0286b050 in ?? () #4 0x0

Re: [Discuss-gnuradio] Segmentation fault using qt gui sink

On Mon, Mar 18, 2013 at 6:47 AM, Volker Schroer wrote: > Sorry, now with example > I've run your example on the current master and not getting a segfault. If there is a way you can get a gdb backtrace and the exact commit ID used I'd appreciate it. Johnathan __

[Discuss-gnuradio] Segmentation fault using qt gui sink

Sorry, now with example Hi all, if I use a qt-gui sink in a flowgraph I get a segmentation fault on the tb.stop() call. That is a problem as I use this together with a wavfile-sink. Due to the segfault the wav file header is not written and I have to use a hexeditor to correct the header d

[Discuss-gnuradio] Segmentation fault using qt gui sink

Hi all, if I use a qt-gui sink in a flowgraph I get a segmentation fault on the tb.stop() call. That is a problem as I use this together with a wavfile-sink. Due to the segfault the wav file header is not written and I have to use a hexeditor to correct the header data to be able to read th

Re: [Discuss-gnuradio] Segmentation fault for aligned volk kernel with custom arrays

On Mon, Nov 12, 2012 at 4:55 AM, "Martin Lülf" wrote: >> On Fri, Nov 9, 2012 at 11:47 AM, "Martin Lülf" wrote: >>> Hi list, >>> >>> I am trying to speed up my own gnuradio block using volk. Besides using >>> volk on gnuradios input and output buffers I also want do use it with my >>> own arrays.

Re: [Discuss-gnuradio] Segmentation fault for aligned volk kernel with custom arrays

> On Fri, Nov 9, 2012 at 11:47 AM, "Martin Lülf" wrote: >> Hi list, >> >> I am trying to speed up my own gnuradio block using volk. Besides using >> volk on gnuradios input and output buffers I also want do use it with my >> own arrays. I found this Thread in the mailing list archive >> http://lis

Re: [Discuss-gnuradio] Segmentation fault for aligned volk kernel with custom arrays

On Fri, Nov 9, 2012 at 11:47 AM, "Martin Lülf" wrote: > Hi list, > > I am trying to speed up my own gnuradio block using volk. Besides using > volk on gnuradios input and output buffers I also want do use it with my > own arrays. I found this Thread in the mailing list archive > http://lists.gnu.o

[Discuss-gnuradio] Segmentation fault for aligned volk kernel with custom arrays

Hi list, I am trying to speed up my own gnuradio block using volk. Besides using volk on gnuradios input and output buffers I also want do use it with my own arrays. I found this Thread in the mailing list archive http://lists.gnu.org/archive/html/discuss-gnuradio/2012-09/msg00055.html which shows

[Discuss-gnuradio] segmentation fault while working with more than 1 input

i have downloaded gr-how-to-write-a-block.tar.gz and able to do make check finally. i have added one more input by modifying howto_square_ff.cc and qa_howto.py...when i do make check it is showing segmentation fault -- View this message in context: http://old.nabble.com/segmentation-fault-while-

Re: [Discuss-gnuradio] Segmentation fault in volk_32f_s32f_multiply_32f_a_sse

On 04/07/2012 02:47 PM, Tom Rondeau wrote: And thanks for being able to check it quickly! The fix has been merged into the code. Just in time for 3.5.3, too (whew). Tom I've observed on other fora: all code starts out rather rough. It's only through use, bug reports, and subsequent fixes th

Re: [Discuss-gnuradio] Segmentation fault in volk_32f_s32f_multiply_32f_a_sse

On Sat, Apr 7, 2012 at 1:08 PM, Alexandru Csete wrote: > On Sat, Apr 7, 2012 at 7:07 PM, Alexandru Csete wrote: >> On Sat, Apr 7, 2012 at 5:35 PM, Tom Rondeau wrote: >>> On Sat, Apr 7, 2012 at 10:19 AM, Alexandru Csete wrote: On Sat, Apr 7, 2012 at 4:13 PM, Tom Rondeau wrote: > On Sat

Re: [Discuss-gnuradio] Segmentation fault in volk_32f_s32f_multiply_32f_a_sse

On Sat, Apr 7, 2012 at 7:07 PM, Alexandru Csete wrote: > On Sat, Apr 7, 2012 at 5:35 PM, Tom Rondeau wrote: >> On Sat, Apr 7, 2012 at 10:19 AM, Alexandru Csete wrote: >>> On Sat, Apr 7, 2012 at 4:13 PM, Tom Rondeau wrote: On Sat, Apr 7, 2012 at 9:48 AM, Alexandru Csete wrote: > Greeti

Re: [Discuss-gnuradio] Segmentation fault in volk_32f_s32f_multiply_32f_a_sse

On Sat, Apr 7, 2012 at 5:35 PM, Tom Rondeau wrote: > On Sat, Apr 7, 2012 at 10:19 AM, Alexandru Csete wrote: >> On Sat, Apr 7, 2012 at 4:13 PM, Tom Rondeau wrote: >>> On Sat, Apr 7, 2012 at 9:48 AM, Alexandru Csete wrote: Greetings, I'm getting segmentation faults in a C++ applic

Re: [Discuss-gnuradio] Segmentation fault in volk_32f_s32f_multiply_32f_a_sse

On Sat, Apr 7, 2012 at 10:19 AM, Alexandru Csete wrote: > On Sat, Apr 7, 2012 at 4:13 PM, Tom Rondeau wrote: >> On Sat, Apr 7, 2012 at 9:48 AM, Alexandru Csete wrote: >>> Greetings, >>> >>> I'm getting segmentation faults in a C++ application when I restart >>> the flow graph, i.e by doing: >>>

Re: [Discuss-gnuradio] Segmentation fault in volk_32f_s32f_multiply_32f_a_sse

On Sat, Apr 7, 2012 at 4:13 PM, Tom Rondeau wrote: > On Sat, Apr 7, 2012 at 9:48 AM, Alexandru Csete wrote: >> Greetings, >> >> I'm getting segmentation faults in a C++ application when I restart >> the flow graph, i.e by doing: >> >> tb->start() >>  ... >> tb->stop() >> tb->wait() >> ... >> tb->

Re: [Discuss-gnuradio] Segmentation fault in volk_32f_s32f_multiply_32f_a_sse

On Sat, Apr 7, 2012 at 9:48 AM, Alexandru Csete wrote: > Greetings, > > I'm getting segmentation faults in a C++ application when I restart > the flow graph, i.e by doing: > > tb->start() >  ... > tb->stop() > tb->wait() > ... > tb->start() > (crashes) > > Running the application through a debugge

[Discuss-gnuradio] Segmentation fault in volk_32f_s32f_multiply_32f_a_sse

Greetings, I'm getting segmentation faults in a C++ application when I restart the flow graph, i.e by doing: tb->start() ... tb->stop() tb->wait() ... tb->start() (crashes) Running the application through a debugger suggests it is volk_32f_s32f_multiply_32f_a_sse which is used by a gr_multiply_

Re: [Discuss-gnuradio] Segmentation Fault or *** glibc detected *** python: double free or corruption (out): 0x0000000002ed6fb0 *** ======= Backtrace: =========

On Mon, Mar 19, 2012 at 9:04 AM, UB wrote: > > I have a very simple gnuradio python code (file source --> RRC filter --> > USRPsink) > What version of GNU Radio are you using? What's your hardware (processor)? And, you can follow this to help nail down where the segfault is occurring: http://gn

[Discuss-gnuradio] Segmentation Fault or *** glibc detected *** python: double free or corruption (out): 0x0000000002ed6fb0 *** ======= Backtrace: =========

I have a very simple gnuradio python code (file source --> RRC filter --> USRPsink) i run the code, and i get either Segmentation Fault, or I get this long error: *** glibc detected *** python: double free or corruption (out): 0x02ed6fb0 *** === Backtrace: = /lib/x86_64-linu

Re: [Discuss-gnuradio] Segmentation fault

I had forgotten to enclose the code, here it goes! # USRP2 sinks # # slave USRP2 self.usrp2_sink_slave = uhd.single_usrp_sink( device_addr="addr=192.168.20.3",

Re: [Discuss-gnuradio] Segmentation fault

Hi, Actually what I'm trying to do is a 2x1 MIMO, but I was trying to run the benchmark with its default set up to see if I had success with the merging. As you said, this segmentation fault must appear somewhere when trying to implement 2 receivers, when you adjust the parameters for 2 tx antenna

Re: [Discuss-gnuradio] Segmentation fault

On Mon, Feb 20, 2012 at 5:48 AM, Jorge Hernandez < jorge.gnura...@googlemail.com> wrote: > Hi all, > > I've been working lately to get to work the mimo files from trondeau's > branch. After some trials, I thought I've successfully merged the master > branch into this branch so I could use the mimo

[Discuss-gnuradio] Segmentation fault

Hi all, I've been working lately to get to work the mimo files from trondeau's branch. After some trials, I thought I've successfully merged the master branch into this branch so I could use the mimo files. However, when trying to run the benchmark_mimo_ofdm.py file a segmentation fault is happen

Re: [Discuss-gnuradio] segmentation fault with current gnuradio version on USRP1

This I did more than 10 times recently, testing also with 3.4.2, carefully deinstalling previously installed versions. It's reasonably fast on 4-core machine and as Gentoo user I am used to run some compilations :-). As I wrote I got compilation errors with newer boost versions, I will retry tha

Re: [Discuss-gnuradio] segmentation fault with current gnuradio version on USRP1

On 02/02/2012 05:54 PM, Nick Foster wrote: Try recompiling gr-uhd and reinstalling. --n Might as well re-do the entire Gnu Radio build. It doesn't take *that* long. -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org __

Re: [Discuss-gnuradio] segmentation fault with current gnuradio version on USRP1

Try recompiling gr-uhd and reinstalling. --n On Thu, Feb 2, 2012 at 2:42 PM, Jiri Pittner wrote: > I have installed git version of UHD drivers and images from > UHD-images-003.004.000-**322fb97.tar.gz. > uhd_usrp_probe runs again well but, > unfortunately, the problem persists: > usrp_wfm_rcv.py

Re: [Discuss-gnuradio] segmentation fault with current gnuradio version on USRP1

I have installed git version of UHD drivers and images from UHD-images-003.004.000-322fb97.tar.gz. uhd_usrp_probe runs again well but, unfortunately, the problem persists: usrp_wfm_rcv.py linux; GNU C++ version 4.5.3; Boost_104700; UHD_003.004.000-5b06adb ... Segmentation fault (core dumped) ...

Re: [Discuss-gnuradio] segmentation fault with current gnuradio version on USRP1

There was an ABI change between Gnu Radio and UHD, so you have to be running a newer UHD--current master is what I'd recommend. Also, you'll find your world is better if you use build-gnuradio, if you're on Ubuntu or Fedora. On Thu, 2 Feb 2012 21:41:50 +0100 (CET), jiri.pitt...@jh-inst.cas.

[Discuss-gnuradio] segmentation fault with current gnuradio version on USRP1

Hello, I would like to ask for an advice - I have troubles running current gnuradio git version with USRP1 using UHD. I have installed UHD drivers with downloaded firmware and FPGA images and compiled the host code; uhd_usrp_probe seems to work: linux; GNU C++ version 4.5.3; Boost_104700; UHD_

Re: [Discuss-gnuradio] Segmentation fault in wav file sink

On Mon, Dec 12, 2011 at 10:52 AM, Martin Braun wrote: > > Yes, that makes sense. Try this (is the same as what I sent to > patch-gnuradio). It works with your script. > FYI, I've run this for the past 24 hours (on the production app, not the test script) and haven't seen any segfaults. _

Re: [Discuss-gnuradio] Segmentation fault in wav file sink

On Mon, Dec 12, 2011 at 10:57 AM, Matt Mills wrote: > > But wont this only close() a file when the sink is receiving samples? I > would think it would be extremely confusing if close() doesnt actually > close a file until the next sample is received, especially if there is a > valve in front of t

Re: [Discuss-gnuradio] Segmentation fault in wav file sink

On Mon, Dec 12, 2011 at 10:47 AM, Martin Braun wrote: > On Mon, Dec 12, 2011 at 11:49:56AM +0100, Martin Braun wrote: > > On Sun, Dec 11, 2011 at 02:31:03PM -0500, Marcus D. Leech wrote: > > > I think that what I'd do is cause the close() method to simply set a > flag that > > > says "close desir

Re: [Discuss-gnuradio] Segmentation fault in wav file sink

On Mon, Dec 12, 2011 at 10:37:35AM -0700, Matt Mills wrote: > On Mon, Dec 12, 2011 at 3:41 AM, Martin Braun wrote: > > * Do you randomly get either segfault or i/o error? I always get the i/o >  with this code.. > > I get both. >   > > * Your code stresses the WAV-code a lot :) What

Re: [Discuss-gnuradio] Segmentation fault in wav file sink

On Mon, Dec 12, 2011 at 11:49:56AM +0100, Martin Braun wrote: > On Sun, Dec 11, 2011 at 02:31:03PM -0500, Marcus D. Leech wrote: > > I think that what I'd do is cause the close() method to simply set a flag > > that > > says "close desired", and then do the actual close at the end of > > the wor

Re: [Discuss-gnuradio] Segmentation fault in wav file sink

On Mon, Dec 12, 2011 at 3:41 AM, Martin Braun wrote: > * Do you randomly get either segfault or i/o error? I always get the i/o > with this code.. > I get both. > * Your code stresses the WAV-code a lot :) What are you trying to > accomplish? Are you finding a bug in wavfile_sink or do you n

Re: [Discuss-gnuradio] Segmentation fault in wav file sink

On Sun, Dec 11, 2011 at 02:31:03PM -0500, Marcus D. Leech wrote: > I think that what I'd do is cause the close() method to simply set a flag that > says "close desired", and then do the actual close at the end of > the work function, probably under a mutex. That sounds sensible. It could be done

Re: [Discuss-gnuradio] Segmentation fault in wav file sink

On Sun, Dec 11, 2011 at 01:18:59AM -0700, Matt Mills wrote: > All, > > The attached script crashes with a segmentation fault (or with the I/O error > text in the code). My C++ knowledge is lacking however I believe this is > because work() and close() are both being called simultaneously from diff

Re: [Discuss-gnuradio] Segmentation fault in wav file sink

If there is no samples flowing into the wav file sink block would work() be called? (IE, if there is a closed valve in front of the wav_file sink) On Sun, Dec 11, 2011 at 12:31 PM, Marcus D. Leech wrote: > ** > I think that what I'd do is cause the close() method to simply set a flag > that say

Re: [Discuss-gnuradio] Segmentation fault in wav file sink

On 12/11/2011 03:18 AM, Matt Mills wrote: All, The attached script crashes with a segmentation fault (or with the I/O error text in the code). My C++ knowledge is lacking however I believe this is because work() and close() are both being called simultaneously from different threads. The clos

[Discuss-gnuradio] Segmentation fault in wav file sink

All, The attached script crashes with a segmentation fault (or with the I/O error text in the code). My C++ knowledge is lacking however I believe this is because work() and close() are both being called simultaneously from different threads. The close() call is being made while the execution of w

Re: [Discuss-gnuradio] Segmentation Fault

On 26/10/2011 11:43 AM, Vanessa Gardellin wrote: I have the same problem, anyone? Vanessa Try this before you start the app: export "LIBGL_ALWAYS_INDIRECT=1" Does that help? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists

Re: [Discuss-gnuradio] Segmentation Fault

I have the same problem, anyone? Vanessa On Wed, Oct 19, 2011 at 1:35 AM, Sriharsha Puranik wrote: > Hi all, > I am facing "Segmentation Fault" error. > My setup is - Ubuntu 11.04, USRP2 with WBX board, gnuradio. > The scenario is - When I run uhd_fft.py, I get the following - > (gdb) run /usr/l

[Discuss-gnuradio] Segmentation Fault

Hi all, I am facing "Segmentation Fault" error. My setup is - Ubuntu 11.04, USRP2 with WBX board, gnuradio. The scenario is - When I run uhd_fft.py, I get the following - (gdb) run /usr/local/bin/uhd_fft.py Starting program: /usr/bin/python /usr/local/bin/uhd_fft.py [Thread debugging using libt

Re: [Discuss-gnuradio] segmentation fault when using a new added block

-tree-project command to change the name of the new package,and other things are same.Why the block of this package can work? From: tianxia...@hotmail.com To: discuss-gnuradio@gnu.org Date: Mon, 18 Apr 2011 16:20:13 +0800 Subject: Re: [Discuss-gnuradio] segmentation fault when using a new added

Re: [Discuss-gnuradio] segmentation fault when using a new added block

r: 'module' object has no attribute 'square_ff'.So how can I do to figure out this problem?I hope someone can tell me .Thanks in advance. inter From: tianxia...@hotmail.com To: discuss-gnuradio@gnu.org Date: Thu, 14 Apr 2011 16:09:01 +0800 Subject: [Discuss-gnuradio] segmentatio

Re: [Discuss-gnuradio] segmentation fault when using a new added block

inal howto file, how did this error happen?I am confused about it. Date: Thu, 14 Apr 2011 13:23:17 +0200 From: martin.br...@kit.edu To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] segmentation fault when using a new added block On Thu, Apr 14, 2011 at 01:19:25PM +0200, Martin Braun w

Re: [Discuss-gnuradio] segmentation fault when using a new added block

On Thu, Apr 14, 2011 at 01:19:25PM +0200, Martin Braun wrote: > On Thu, Apr 14, 2011 at 04:09:01PM +0800, intermilan wrote: > > do not know why does this error happen. > > I did not change anything in the gr-howto-write-a-block-3.3.0. I hope > > someone > > can help me to fix this problem and > >

Re: [Discuss-gnuradio] segmentation fault when using a new added block

On Thu, Apr 14, 2011 at 04:09:01PM +0800, intermilan wrote: > do not know why does this error happen. > I did not change anything in the gr-howto-write-a-block-3.3.0. I hope someone > can help me to fix this problem and > tell me why this error happen. Not without seeing your code. Most often, thi

[Discuss-gnuradio] segmentation fault when using a new added block

hi all: I want to use the gr-howto-write-a-block-3.3.0 (my version of the Gnuradio is 3.3.0)to add a new package or a new block to the gnuradio and grc. At first I did not change anything in the gr-howto-write-a-block-3.3.0, so the name of the new package should be howto,and the name of the

Re: [Discuss-gnuradio] segmentation fault (core dump) -- help needed

ject: Re: [Discuss-gnuradio] segmentation fault (core dump) -- help needed Sent by:discuss-gnuradio-bounces+thomas.h.kim=aero@gnu.org On Mon, Nov 8, 2010 at 12:13 PM, Steven Clark wrote: > On Mon, Nov 8, 2010 at 11:52 AM, Thomas H Kim wrote: >> >> Steven, >

Re: [Discuss-gnuradio] segmentation fault (core dump) -- help needed

On Mon, Nov 8, 2010 at 12:13 PM, Steven Clark wrote: > On Mon, Nov 8, 2010 at 11:52 AM, Thomas H Kim wrote: >> >> Steven, >> >> Thank you very much for your email. >> I installed Fedora Core13  x86_64, instead of i386, which I installed on >> last Friday and it works now. But, I don't understand

Re: [Discuss-gnuradio] segmentation fault (core dump) -- help needed

On Mon, Nov 8, 2010 at 11:52 AM, Thomas H Kim wrote: > Steven, > > Thank you very much for your email. > I installed Fedora Core13 x86_64, instead of i386, which I installed on > last Friday and it works now. But, I don't understand because i386 should > work on 64bit machine (that was what I've

Re: [Discuss-gnuradio] segmentation fault (core dump) -- help needed

On Mon, Nov 8, 2010 at 7:59 AM, Martin Braun wrote: > > Even in an old version, this should not happen. However, if you do have > an old version, I recommend upgrading to at least 3.3.0 and trying > again. Once it works, you'll simply have much more fun (read: > functionality) with a newer GNU Ra

Re: [Discuss-gnuradio] segmentation fault (core dump) -- help needed

On Mon, Nov 08, 2010 at 07:42:25AM -0500, Thomas H Kim wrote: > I installed Fedora Core 14 and installed all needed dependencies using YUM as > shown below. > > yum groupinstall "Engineering and Scientific" "Development Tools" > yum install fftw-devel cppunit-devel wxPython-devel libusb-devel guil

[Discuss-gnuradio] segmentation fault (core dump) -- help needed

Hi all, I'm a newbie in gnu software radio (and in python, and in linux) and got stuck on this segmentation fault issue. I am trying to setup GNU software radio on a machine (HP workstation xw8600 with dual intel Xeon processor). I installed Fedora Core 14 and installed all needed dependencies

[Discuss-gnuradio] Segmentation fault in usrp_siggen.py hier_block

Hi all, I'm trying to define a hier_block with the same functionality as the usrp_siggen top_block. The main idea is to use this new block in a dynamic way changing the frequency and/or the amplitude of the signal. I did "copy/paste" of the code of usrp_siggen.py and I put it on a hier_block2

Re: [Discuss-gnuradio] Segmentation fault when "make check"

On Tue, Sep 01, 2009 at 03:51:41PM -0700, Milo Wong wrote: > Hi All, > > I was writing a new block and the "make" process of source files(.cc .h .i, > etc) was successful. However, when I "make check" to test the block, there's > an error message "Segmentation fault" coming out. I searched the pre

[Discuss-gnuradio] Segmentation fault when "make check"

Hi All, I was writing a new block and the "make" process of source files(.cc .h .i, etc) was successful. However, when I "make check" to test the block, there's an error message "Segmentation fault" coming out. I searched the previous discussions but there were not too much useful information. I k

Re: [Discuss-gnuradio] Segmentation fault : Try to make dual channel building blocks

On Fri, Mar 06, 2009 at 05:22:44PM -0800, Yong J. Chang wrote: > > Thank you Eric, > > But I still have a problem. I simply made two blocks. > > 1) First One > gr_data_parser::gr_data_parser () > : gr_block ("gr_data_parser", > gr_make_io_signature (1, 1, sizeof (gr_complex))

Re: [Discuss-gnuradio] Segmentation fault : Try to make dual channel building blocks

Thank you Eric, But I still have a problem. I simply made two blocks. 1) First One gr_data_parser::gr_data_parser () : gr_block ("gr_data_parser", gr_make_io_signature (1, 1, sizeof (gr_complex)), gr_make_io_signature (1, 2, sizeof (gr_complex))) 2) Seco

Re: [Discuss-gnuradio] Segmentation fault : Try to make dual channel building blocks

On Fri, Mar 06, 2009 at 11:03:28AM -0800, Yong J. Chang wrote: > > Hi all, > > Now I'm building some signaling blocks having dual output streams. > But if I try to make dual output streams which have different data type from > input stream, 'Segmentation fault' error is occurred. How can I make d

[Discuss-gnuradio] Segmentation fault : Try to make dual channel building blocks

Hi all, Now I'm building some signaling blocks having dual output streams. But if I try to make dual output streams which have different data type from input stream, 'Segmentation fault' error is occurred. How can I make dual outputs which have different data type from input stream? Thanks in ad

Re: [Discuss-gnuradio] Segmentation fault (core dump)

Arrrgh! Apologies to all. I totally missed the all-important "2" at the end of Irene's gr_make_io_signature2 call. Please ignore my previous post. @(^.^)@ Ed Ed Criscuolo wrote: Irene, I believe the problem is that you are trying to have two different types of output streams. According t

  1   2   >