ryanvolz / radioconda

Software radio distribution and installer for conda
Other
342 stars 39 forks source link

Return code 3221225501 #10

Closed riocorre closed 1 year ago

riocorre commented 2 years ago

Hi,

I have installed GNU Radio 3.9.5.0 on Windows 10. I have a simple configuration of a RTL-SDR sink and QT GUI Sink.

The error makes end the program with this code: Return code 3221225501 It also happens with QT GUI Frequency Sink.

It does not happen with QT Time Sink.

Do you have some hints about it?

Thanks!

Enrique

ryanvolz commented 2 years ago

Hi Enrique!

I take this to mean that your flowgraph does not run at all, immediately crashing with that error code? Does it say anything else before that happens?

Some searching seems to indicate that that error code is related to being unable to load a DLL. How are you running GNU Radio Companion? (e.g. from the Start Menu entry called "GNU Radio Companion (radioconda)", or by running gnuradio-companion from the "Conda Prompt (radioconda)"). It's possible that it can't find a DLL because the conda environment has not been activated properly by running using one of those methods.

riocorre commented 2 years ago

Hi Ryan,

thank you for your email.

I have the same error If I run the application from the Start Menu or by the Condia Prompt.

I add some images.

[image: image.png] [image: image.png] [image: image.png]

[image: image.png]

Thanks!

Enrique

On Sat, Feb 12, 2022, 20:16 Ryan Volz @.***> wrote:

Hi Enrique!

I take this to mean that your flowgraph does not run at all, immediately crashing with that error code? Does it say anything else before that happens?

Some searching seems to indicate that that error code is related to being unable to load a DLL. How are you running GNU Radio Companion? (e.g. from the Start Menu entry called "GNU Radio Companion (radioconda)", or by running gnuradio-companion from the "Conda Prompt (radioconda)"). It's possible that it can't find a DLL because the conda environment has not been activated properly by running using one of those methods.

— Reply to this email directly, view it on GitHub https://github.com/ryanvolz/radioconda/issues/10#issuecomment-1037447348, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXSFGAG2AYWUDV65DUBOK3U225Z7ANCNFSM5OHLRWXQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

ryanvolz commented 2 years ago

Hi Enrique,

The images didn't come through Github's system. I think you'll have to use the website to post them to the issue.

riocorre commented 2 years ago

Thank you Ryan,

here you have the images,

Cheers, image image (1) image (2) image (3)

Enrique

riocorre commented 2 years ago

Hi, Ryan, here are the images. image image (1) image (2) image (3)

riocorre commented 2 years ago

Hi Ryan,

I have uploaded the images at Github, did you received them?

Enrique

On Sun, Feb 13, 2022, 15:34 Ryan Volz @.***> wrote:

Hi Enrique,

The images didn't come through Github's system. I think you'll have to use the website to post them to the issue.

— Reply to this email directly, view it on GitHub https://github.com/ryanvolz/radioconda/issues/10#issuecomment-1038198281, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXSFGBVFLPMWTU6JOCTOU3U27FQRANCNFSM5OHLRWXQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

ryanvolz commented 2 years ago

Hi Enrique,

This is a tough one. That error code is not much to go on, and that's the only clue we have besides that fact that it works for the Qt Time sink but not the GUI sink. I tried your exact flowgraph and it worked fine for me, so that doesn't help.

Maybe we can figure out what is different about your system, specifically related to Qt since that seems to be a culprit. Do you have any other versions of GNU Radio installed (e.g. GNCDevelopment, PothosSDR), or have they been installed in the past? Interference with old/other installations has sometimes been a problem. How about Qt being installed somewhere else as well? Any other applications installed that you know use Qt and may have brought and incompatible version? Anything else special about your setup that might be relevant?

Failing progress from that, maybe the next step would be to launch ipython from the Conda Prompt and then manually enter the Python script produced by your failing flowgraph line-by-line, until we can see what line causes the segmentation fault.

riocorre commented 2 years ago

Thank you Ryan.

It is the first time I installed GNU radio on this computer.

Enrique

On Mon, Feb 14, 2022, 16:19 Ryan Volz @.***> wrote:

Hi Enrique,

This is a tough one. That error code is not much to go on, and that's the only clue we have besides that fact that it works for the Qt Time sink but not the GUI sink. I tried your exact flowgraph and it worked fine for me, so that doesn't help.

Maybe we can figure out what is different about your system, specifically related to Qt since that seems to be a culprit. Do you have any other versions of GNU Radio installed (e.g. GNCDevelopment, PothosSDR), or have they been installed in the past? Interference with old/other installations has sometimes been a problem. How about Qt being installed somewhere else as well? Any other applications installed that you know use Qt and may have brought and incompatible version? Anything else special about your setup that might be relevant?

Failing progress from that, maybe the next step would be to launch ipython from the Conda Prompt and then manually enter the Python script produced by your failing flowgraph line-by-line, until we can see what line causes the segmentation fault.

— Reply to this email directly, view it on GitHub https://github.com/ryanvolz/radioconda/issues/10#issuecomment-1039266426, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXSFGDAMH2LGRRZOMLFLZ3U3ESEDANCNFSM5OHLRWXQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

ryanvolz commented 2 years ago

I think running the flowgraph-generated script manually line-by-line is your next best bet for narrowing this down. That should at least tell us what line is causing the error, and maybe it gives you a better error message. I suggest using an ipython interactive session.

riocorre commented 2 years ago

Thank you Ryan.

I will let it as is by the moment.

Enrique

On Tue, Feb 15, 2022, 17:06 Ryan Volz @.***> wrote:

I think running the flowgraph-generated script manually line-by-line is your next best bet for narrowing this down. That should at least tell us what line is causing the error, and maybe it gives you a better error message. I suggest using an ipython interactive session.

— Reply to this email directly, view it on GitHub https://github.com/ryanvolz/radioconda/issues/10#issuecomment-1040541322, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXSFGFBONSBUBYJGOUZB23U3KBZNANCNFSM5OHLRWXQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

ryanvolz commented 1 year ago

I think this is better summarized in #25.