Re: [Discuss-gnuradio] swig/python memory leak

2013-05-28 Thread Ralph A. Schmid, dk5ras
Hi, > I've already started to do this with gr-osmosdr. Right now, I've > updated their > interface to the RTL-SDR (tested) and HackRF (untested) to compile > against the new master branch of GNU Radio. You can use my repo here > as a remote with your current gr-osmosdr to get the gr-next branc

Re: [Discuss-gnuradio] swig/python memory leak

2013-05-28 Thread Nada ABDELKADER
The .i file includes the .h file where "my_type" is defined. isn't that enough? Josh Blum a écrit : On 05/27/2013 11:10 AM, Nada ABDELKADER wrote: Hi, May be this is not the appropriate place to post this problem but I'm working on gnuradio and USRPs and trying to access c++ objects from

Re: [Discuss-gnuradio] swig/python memory leak

2013-05-27 Thread Josh Blum
On 05/27/2013 11:10 AM, Nada ABDELKADER wrote: > Hi, > > May be this is not the appropriate place to post this problem but I'm > working on gnuradio and USRPs and trying to access c++ objects from python. > Every thing works well, but in each call I got this display: > > swig/python detected a