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
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
__
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
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
