25 Jun
2017
25 Jun
'17
3:35 a.m.
After a successful build of the Gnuradio plus extras by modifying the
build-gnuradio script to point to the osmocom git repository for rtlsdr,
I get an error and backtrace/memory map similar to the attached
osmosdr-error-output.txt when I exit from, e.g., osmo_fft (the program
seems to run fine until exit). Fabian suggested that I post this to the
list.
I also installed op25 on this system, and it fails at runtime with a
bunch of errors that I'm attaching as "op25-error-output.txt"; the end
of the sring is:
wx._core.PyAssertionError: C++ assertion "!m_frameStatusBar" failed at
../src/common/framecmn.cpp(381) in CreateStatusBar(): recreating status
bar in wxFrame
I wonder if this error is related, as op25 on a several-month-old
gnuradio installation works fine.
Thanks for any pointers on how to resolve this issue (or these issues).
John
-------- Forwarded Message --------
Subject: Re: Problem with latest version (master) of gr-osmosdr
Date: Sat, 24 Jun 2017 14:35:45 -0400
From: John Ackermann N8UR <jra(a)febo.com>
To: kerel <kerel-fs(a)gmx.de>
Here you go, Fabian. Thanks much for looking into this!
I have noticed this problem each time I've managed to get a successful
build-gnuradio completion on this system (e.g., after I commented out
the changes that made the build fail). I have another machine that was
updated using build-gnuradio perhaps three months ago, and it does not
exhibit this behavior.
One difference is that the other machine is running Linux Mint 18.0,
while the current one is on 18.1 (both "apt-get dist-upgraded" to
current levels at the time of the build).
John
----
On 06/24/2017 02:23 PM, kerel wrote:
Hi John,
this seems like an unrelated issue in gr-osmosdr, but I can't tackle it
with the partial? backtrace you provided and can't reproduce it myself.
Could you provide the full backtrace?
Sincerely,
Fabian
25 Jun
25 Jun
3:41 a.m.
Sorry, didn't attach the op25 console output to the previous message.
Here it is.
On 06/24/2017 09:35 PM, John Ackermann N8UR wrote:
After a successful build of the Gnuradio plus extras
by modifying the
build-gnuradio script to point to the osmocom git repository for rtlsdr,
I get an error and backtrace/memory map similar to the attached
osmosdr-error-output.txt when I exit from, e.g., osmo_fft (the program
seems to run fine until exit). Fabian suggested that I post this to the
list.
I also installed op25 on this system, and it fails at runtime with a
bunch of errors that I'm attaching as "op25-error-output.txt"; the end
of the sring is:
wx._core.PyAssertionError: C++ assertion "!m_frameStatusBar" failed at
../src/common/framecmn.cpp(381) in CreateStatusBar(): recreating status
bar in wxFrame
I wonder if this error is related, as op25 on a several-month-old
gnuradio installation works fine.
Thanks for any pointers on how to resolve this issue (or these issues).
John
-------- Forwarded Message --------
Subject: Re: Problem with latest version (master) of gr-osmosdr
Date: Sat, 24 Jun 2017 14:35:45 -0400
From: John Ackermann N8UR <jra(a)febo.com>
To: kerel <kerel-fs(a)gmx.de>
Here you go, Fabian. Thanks much for looking into this!
I have noticed this problem each time I've managed to get a successful
build-gnuradio completion on this system (e.g., after I commented out
the changes that made the build fail). I have another machine that was
updated using build-gnuradio perhaps three months ago, and it does not
exhibit this behavior.
One difference is that the other machine is running Linux Mint 18.0,
while the current one is on 18.1 (both "apt-get dist-upgraded" to
current levels at the time of the build).
John
----
On 06/24/2017 02:23 PM, kerel wrote:
Hi John,
this seems like an unrelated issue in gr-osmosdr, but I can't tackle
it with the partial? backtrace you provided and can't reproduce it
myself.
Could you provide the full backtrace?
Sincerely,
Fabian
3:57 a.m.
Apologies for the further interruption... the example I gave shows
running scope.py with no parameters. I get similar results if I run
with a command line that was cut-and-pasted from my other, working, system.
On 06/24/2017 09:41 PM, John Ackermann N8UR wrote:
Sorry, didn't attach the op25 console output to
the previous message.
Here it is.
On 06/24/2017 09:35 PM, John Ackermann N8UR wrote:
> After a successful build of the Gnuradio plus extras by modifying the
> build-gnuradio script to point to the osmocom git repository for
> rtlsdr, I get an error and backtrace/memory map similar to the
> attached osmosdr-error-output.txt when I exit from, e.g., osmo_fft
> (the program seems to run fine until exit). Fabian suggested that I
> post this to the list.
>
> I also installed op25 on this system, and it fails at runtime with a
> bunch of errors that I'm attaching as "op25-error-output.txt"; the end
> of the sring is:
>
> wx._core.PyAssertionError: C++ assertion "!m_frameStatusBar" failed at
> ../src/common/framecmn.cpp(381) in CreateStatusBar(): recreating
> status bar in wxFrame
>
> I wonder if this error is related, as op25 on a several-month-old
> gnuradio installation works fine.
>
> Thanks for any pointers on how to resolve this issue (or these issues).
>
> John
> -------- Forwarded Message --------
> Subject: Re: Problem with latest version (master) of gr-osmosdr
> Date: Sat, 24 Jun 2017 14:35:45 -0400
> From: John Ackermann N8UR <jra(a)febo.com>
> To: kerel <kerel-fs(a)gmx.de>
>
> Here you go, Fabian. Thanks much for looking into this!
>
> I have noticed this problem each time I've managed to get a successful
> build-gnuradio completion on this system (e.g., after I commented out
> the changes that made the build fail). I have another machine that
> was updated using build-gnuradio perhaps three months ago, and it does
> not exhibit this behavior.
>
> One difference is that the other machine is running Linux Mint 18.0,
> while the current one is on 18.1 (both "apt-get dist-upgraded" to
> current levels at the time of the build).
>
> John
> ----
>
> On 06/24/2017 02:23 PM, kerel wrote:
>> Hi John,
>> this seems like an unrelated issue in gr-osmosdr, but I can't tackle
>> it with the partial? backtrace you provided and can't reproduce it
>> myself.
>> Could you provide the full backtrace?
>>
>> Sincerely,
>> Fabian
>
2506
days inactive
2506
days old
2 comments
1 participants
participants (1)
-
John Ackermann N8UR