Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Activecat
Mostafa, I do not think you have truly run the complete codes using Qtcreator, because that doesn't have a gnuradio runtime (the scheduler). At the other hand, your problem sounds more like a c++ coding error rather than gnuradio-specific. The helpful approach is 1). Put up the OOT into github.

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Mostafa Alizadeh
I forgot to say, I'm using Qtcreator to debug my GNURadio codes I do not need any others! The prgram is terminated at line in which I read from the input for the first time i.e. : y_p[i][k] = 0; for (int j=0; j wrote: > Yes you're right about casting between "in" and "input_i

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Mostafa Alizadeh
Yes you're right about casting between "in" and "input_items", however, I think this problem is somehow related to the large number input ports! I don't why! Here is the whole block: #ifdef HAVE_CONFIG_H #include "config.h" #endif #include #include "phich_grouping_impl.h" int N_FS_phich(bool n

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Marcus Müller
As I said, you should use the gdb debugging approach to find the mistake. gr_complex **in = (gr_complex) input_items; shouldn't compile, because the types are incompatible. I can't help you any further with the information you're offering. Please share at least your complete general_work method, a

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Mostafa Alizadeh
Thank you for your notes Marcus, As you said this is unnecessary process to point to the input_items in a for loop!! However, this is not the problem because I checked that I have the same number of iteration in the for loop as the number of input ports. The problem is somewhere else. *Again I mu

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Marcus Müller
Having your complete general_work function wouldn't have hurt my understanding much... I really can't make out what you're trying to do without doubt. Anyway, from the code below I think "in" *must at least* have the same number of entries that your for loop has iterations; did you just try using

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-26 Thread Mostafa Alizadeh
Hi Marcus, You're right. I didn't clarify the problem. Actually in C++, I wrote: block_impl::block_impl(bool normal, int group) : gr::block("phich_grouping", gr::io_signature::make(1, group * N_FS(normal), sizeof (gr_complex)), gr::io_signature::make(1, 1, s

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-26 Thread Marcus Müller
Hi Mostafa, indeed, this sounds strange. However, with but the information you offered, it will be hard to determine what goes wrong. Would you have more information, e.g. when exactly this happens, is this C++ or python, do you have source code, in which code line the error occurs (hint: [1])?

[Discuss-gnuradio] Problem with large number of inputs.

2014-07-26 Thread Mostafa Alizadeh
Hi all, I've used to have a block with large number of inputs, say 24, but I think GNURadio has a problem with memory allocation because when I use the block it's suddenly jump out of the program with "The program has unexpectedly finished." (the above message isn't for GNURadio) However, when