Hi Franco.
Thank you so much for the trace information.
Very helpful and, i'm having fun poking around under the hood.
233 execve("/usr/bin/gnuradio-companion", ["gnuradio-companion",
"/UNUSED/testing123.grc"], 0x7fffb6e6d940 /* 8 vars */) = 0
247 execve("/usr/bin/dbus-launch", ["dbus-launch", "--autolaunch",
"95afc6e6d7a14382a620df11724dd0ec", "--binary-syntax", "--close-stderr"],
0x719900 /* 8 vars */) = 0
249 execve("/usr/bin/dbus-daemon", ["/usr/bin/dbus-daemon",
"--syslog-only", "--fork", "--print-pid", "5", "--print-address", "7",
"--session"], 0x7fff2a2c23e8 /* 8 vars */) = 0
253 execve("/usr/libexec/at-spi-bus-launcher",
["/usr/libexec/at-spi-bus-launcher"], 0xe44c00 /* 11 vars */) = 0
257 execve("/usr/bin/dbus-daemon", ["/usr/bin/dbus-daemon",
"--config-file=/usr/share/default"..., "--nofork", "--print-address", "3"],
0x7ffdaf0ca728 /* 11 vars */) = 0
258 execve("/usr/bin/gsettings", ["gsettings", "get",
"org.gnome.desktop.interface", "gtk-theme"], 0x719900 /* 8 vars */) = 0
275 execve("/usr/bin/dbus-launch", ["dbus-launch",
"--autolaunch=95afc6e6d7a14382a62"..., "--binary-syntax",
"--close-stderr"], 0x719900 /* 8 vars */) = 0
310 execve("/usr/libexec/at-spi2-registryd",
["/usr/libexec/at-spi2-registryd", "--use-gnome-session"], 0x9f7d30 /* 11
vars */) = 0
314 execve("/usr/bin/python3", ["/usr/bin/python3", "-u",
"/UNUSED/testing123.py"], 0x719900 /* 8 vars */) = 0
On Sun, Feb 13, 2022 at 11:04 AM Franco VENTURI <fvent...@comcast.net>
wrote:
> Steve,
> I am glad to hear that you are now able to run GNU Radio Companion there.
> I am not familiar with the internals of GTK and GObjects and I can't
> really help you there.
>
> However this morning I ran GRC on a simple FM receiver example I have, and
> I used strace to track the calls to 'execve':
>
> strace -f -e execve -o /tmp/grc.trc gnuradio-companion
> FM-Receiver-RSPdx.grc
>
> The output from 'strace' here shows only these processes being launched
> directly by GRC:
>
> 6439 execve("/usr/local/bin/gnuradio-companion", ["gnuradio-companion",
> "FM-Receiver-RSPdx.grc"], 0x7ffc04bea340 /* 75 vars */) = 0
> 6450 execve("/bin/gsettings", ["gsettings", "get",
> "org.gnome.desktop.interface", "gtk-theme"], 0x55652906a3d0 /* 75 vars */)
> = 0
> 6456 execve("/usr/bin/python3", ["/usr/bin/python3", "-uc", "import runpy;
> runpy.run_path('/u"...], 0x55652906a3d0 /* 75 vars */) = 0
> 6529 execve("/usr/bin/python3", ["/usr/bin/python3", "-u",
> "/home/franco/SDR/gr-sdrplay3/exa"...], 0x55652906a3d0 /* 75 vars */) = 0
>
> I don't see GRC launching other additional processes directly; in my case
> some of processes you show in your message are part of the OS common
> services (for instance here I see a service called 'dbus-broker').
>
> Franco
>
>
> On 02/12/2022 10:25 PM Steven Barbo <ba...@umn.edu> wrote:
>
>
> Hello patient and helpful folks, hope this day finds you well.
> Have had some "success", gui runs appears work fine, not calling the
> offending functions g_free and ffi_closure_free in
> gobject-introspection-1.70.0/girepository/girffi.c
>
> guessing these are the parameter linkages and walking trail for
> circuit path for each block etc.?
> no idea where this is even called from, wow there is a lot going on...
>
> **
> * g_callable_info_free_closure:
> * @callable_info: a callable info from a typelib
> * @closure: ffi closure
> *
> * Frees a ffi_closure returned from g_callable_info_prepare_closure()
> */
> void
> g_callable_info_free_closure (GICallableInfo *callable_info,
> ffi_closure *closure)
> {
> GIClosureWrapper *wrapper = (GIClosureWrapper *)closure;
>
> //g_free (wrapper->ffi_closure.cif->arg_types);
> //ffi_closure_free (wrapper->writable_self);
>
> printf("%s ( [callable_info-> dummy1=%d, dummy2=%d, dummy3=%x,
> dummy4=%x, dummy5=%x, dummy6=%d, dummy7=%d,
> padding[0]=%x,padding[1]=%x,padding[2]=%x,padding[3]=%x], [closure-> ... ]
> )\n",__func__,callable_info->dummy1,callable_info->dummy2,callable_info->dummy3,callable_info->dummy4,callable_info->dummy3,callable_info->dummy6,callable_info->dummy7,callable_info->padding[0],callable_info->padding[1],callable_info->padding[2],callable_info->padding[3]);
>
> }
>
>
> typedef struct _GIBaseInfoStub {
> /* <private> */
> gint32 dummy1;
> gint32 dummy2;
> gpointer dummy3;
> gpointer dummy4;
> gpointer dummy5;
> guint32 dummy6;
> guint32 dummy7;
> gpointer padding[4];
> } GIBaseInfo;
>
> /**
> * GICallableInfo:
> *
> * Represents a callable, either #GIFunctionInfo, #GICallbackInfo or
> * #GIVFuncInfo.
> */
>
> 5.1# gnuradio-companion --log debug
>
> [DEBUG] Starting GNU Radio Companion (3.10.2) (main.py:70)
> [DEBUG] Loading platform (main.py:76)
> [DEBUG] Loading application (main.py:86)
> [DEBUG] Running (main.py:88)
> <<< Welcome to GNU Radio Companion 3.10.1.1 >>>
>
> Block paths:
> /usr/share/gnuradio/grc/blocks
>
> Loading: "/UNUSED/testing123.grc"
> >>> Done
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=6,
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=529188, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=6,
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=529188, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
>
> Generating: '/UNUSED/testing123.py'
>
> Executing_callable_info_free_closure ( [callable_info-> dummy1=2,
> dummy2=3, dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=52,
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=76,
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=75,
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=74,
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )g:
> /usr/bin/python3 -u /UNUSED/testing123.py
> ...
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=5,
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=4,
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=3,
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> >>> Done
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=3,
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0,
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> sh-5.1#
>
> one last question, i've never paid attention to a running
> gnuradio-companion, it launces several other processes:
> 6456 tty2 Sl 0:02 /usr/bin/python3 /usr/bin/gnuradio-companion
> 6473 tty2 S 0:00 dbus-launch --autolaunch
> 95afc6e6d7a14382a620df11724dd0ec --binary-syntax --close-stderr
> 6474 ? Ss 0:00 /usr/bin/dbus-daemon --syslog-only --fork
> --print-pid 5 --print-address 7 --session
> 6476 ? Sl 0:00 /usr/libexec/at-spi-bus-launcher
> 6480 ? S 0:00 /usr/bin/dbus-daemon
> --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork
> --print-address 3
> 6534 ? Sl 0:00 /usr/libexec/at-spi2-registryd
> --use-gnome-session
>
> seems a few of these may not normally needed...?
>
> Thanks for for your continued patience and help.
>
>
>
> On Tue, Feb 8, 2022 at 1:26 PM Franco VENTURI <fvent...@comcast.net>
> wrote:
>
> Steve,
> I run Fedora version 35 here, and the version of goobject-introspection I
> have is 1.70:
>
> $ rpm -q gobject-introspection
> gobject-introspection-1.70.0-1.fc35.x86_64
>
> I have GNU Radio 3.10 (actually 3.11 from master) and GNU Radio Companion
> running here without any problem, so perhaps you may just want to remove
> the older 1.69 version from your system, rebuild GNU Radio (or just GRC),
> and see if it works.
>
> Franco
>
> On 02/08/2022 1:57 PM Steven Barbo <ba...@umn.edu> wrote:
>
>
> Hi Franco.
> think i've built trying both versions, 1 at a time obviously.
> didn't seem to make a difference.
> on that front, https://gitlab.gnome.org/GNOME/gobject-introspection
> sports only 1.69 and 1.70 in releases section.
> https://download.gnome.org/sources/gobject-introspection/ has all
> maybe the ones on gitlab are somehow different?...
> will try rebuild with older version assuming that still plays well with
> glib-2.70.2 - anyone using gobject-introspection-1.70 ?
> hunting source is always an adventure.
> Thank you for looking at this, much appreciated.
>
> On Tue, Feb 8, 2022 at 12:29 PM Franco VENTURI <fvent...@comcast.net>
> wrote:
>
> Steve,
> in your list I see two different version of the 'gobject-introspection'
> package:
>
> - gobject-introspection-1.69.0
> - gobject-introspection-1.70.0
>
> Perhaps one of them was used during the build of GNU Radio Companion,
> while the other one is used at runtime when you run 'gnuradio-companion'?
>
> Franco
>
> On 02/08/2022 10:10 AM Steven Barbo via GNU Radio, the Free & Open-Source
> Toolkit for Software Radio <discuss-gnuradio@gnu.org> wrote:
>
>
> Howdy Josh.
> Thank you for your reply, sorry i should have provided more detail.
> OS is bootstrapped, "always roll your own" (tm) , old school stubborn :)
> i've several iterations done this way over the years.
> As a minimalist, ever amazed at all the bloat that can accompany various
> packages, the myriad option available to configure such.
> We all know headaches associated the cruft of stale headers and whatnot.
> My goal, absolute minimum to have gnuradio - no "unnecessary" -
> especially, the overhead of desktops and doctools, systemd and ... getting
> more difficult as time passes... an appliance so to speak.
> i've told myself i'd document the steps and order but, alas, i never seem
> to have the patience.
> pip3 seems to work it's magic, all other packages were compiled
> accordingly - think all dependencies have been met.
> attached gr config and a (partial) list of packages if that's of any help.
> as i said, GUI shows up briefly. way over my head all things things work
> together.
> Thank you are all you patience and help.
>
>
>
> On Tue, Feb 8, 2022 at 5:39 AM Josh Morman <jmor...@gnuradio.org> wrote:
>
> Hi Steve,
>
> Can you please share more information about how GR is installed in your
> case
> - OS/distribution?
> - Installation method (compiled from source, distro packages?
>
> Thanks!
> Josh
>
> On Mon, Feb 7, 2022 at 7:58 PM Steven Barbo <ba...@umn.edu> wrote:
>
> Hello all, hope this day finds you well.
> Having issue with gnuradio-companion, GUI comes up briefly...
>
> dmesg
> [ 1341.843803] traps: gnuradio-compan[372] general protection fault
> ip:7f81ca4f77c8 sp:7f81c7137010 error:0 in
> libgirepository-1.0.so.1.0.0[7f81ca4ed000+20000]
>
>
> have compiled various gr versions over the years, they have always just
> worked :)
>
> any help or pointers are very much appreciated. what an amazing tool,
> thank you.
>
> gnuradio-config --print-all
> /usr/
> /etc
> /etc/gnuradio/conf.d
> /.gnuradio
> Mon, 07 Feb 2022 03:07:35Z
> testing-support;python-support;post-install;man-pages;gnuradio-runtime;common-precompiled-headers;gr-ctrlport;*
> thrift;gnuradio-companion;gr-blocks;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-audio;*
> alsa;*
> oss;gr-channels;gr-pdu;gr-qtgui;gr-trellis;gr-utils;gr_modtool;gr_blocktool;gr-video-sdl;gr-vocoder;*
> gsm;gr-wavelet;gr-network;gr-soapy
> 3.10.1.1
> cc (The Illustrious Industries, Ltd.) 10.3.0
> Copyright (C) 2020 Free Software Foundation, Inc.
> This is free software see the source for copying conditions. There is NO
> warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> c++ (The Illustrious Industries, Ltd.) 10.3.0
> Copyright (C) 2020 Free Software Foundation, Inc.
> This is free software see the source for copying conditions. There is NO
> warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> /usr/bin/cc:::-g -O2 -fvisibility=hidden -Wsign-compare -Wall
> -Wno-uninitialized
> /usr/bin/c++:::-g -O2 -fvisibility=hidden -Wsign-compare -Wall
> -Wno-uninitialized
> 2.9.0
>
>
> apologies for the ugly script and gdb output, tried to disable control
> characters...
> shorten so as to not pollute
>
> sh-5.1# gdb -q /bin/python3 core
> ^[[?2004l^MReading symbols from ^[[32m/bin/python3^[[m...
> ^M
> warning: Can't open file /SYSV00000000 (deleted) during file-backed
> mapping note processing^M
> ^M
> warning: core file may not match specified executable file.^M
> [New LWP 372]^M
> [New LWP 358]^M
> [New LWP 359]^M
> [New LWP 361]^M
> [New LWP 360]^M
> [New LWP 363]^M
> [New LWP 362]^M
> [New LWP 370]^M
> [New LWP 364]^M
> [New LWP 369]^M
> [New LWP 367]^M
> [New LWP 368]^M
> [New LWP 387]^M
> [New LWP 365]^M
> [New LWP 366]^M
> [New LWP 395]^M
> [New LWP 357]^M
> ^M
> warning: Cannot parse .gnu_debugdata section; LZMA support was disabled at
> compile time^M
> [Thread debugging using libthread_db enabled]^M
> Using host libthread_db library "^[[32m/lib64/libthread_db.so.1^[[m".^M
> Core was generated by `/usr/bin/python3 /usr/bin/gnuradio-companion --log
> critical'.^M
> Program terminated with signal SIGSEGV, Segmentation fault.^M
> ^[[?2004h--Type <RET> for more, q to quit, c to continue without
> paging--^M
> ^[[?2004l^M#0 ^[[34m0x00007f81ca4f77c8^[[m in
> ^[[33mg_callable_info_free_closure^[[m (^M
> ^[[36mcallable_info^[[m=0x7f81c00034f0,
> ^[[36mclosure^[[m=0x7f81c9cf3f20)^M
> at ^[[32m../girepository/girffi.c^[[m:428^M
> 428 g_free (wrapper->ffi_closure.cif->arg_types);^M
> [Current thread is 1 (Thread 0x7f81c7138640 (LWP 372))]^M
> ^[[?2004h(gdb) bt^M
> ^[[?2004l^M#0 ^[[34m0x00007f81ca4f77c8^[[m in
> ^[[33mg_callable_info_free_closure^[[m (^M
> ^[[36mcallable_info^[[m=0x7f81c00034f0,
> ^[[36mclosure^[[m=0x7f81c9cf3f20)^M
> at ^[[32m../girepository/girffi.c^[[m:428^M
> #1 ^[[34m0x00007f81c9a83a56^[[m in ^[[33m_pygi_invoke_closure_free^[[m
> (^[[36mdata^[[m=0x7f81c0001630)^M
> at ^[[32mgi/pygi-closure.c^[[m:635^M
> #2 ^[[34m0x00007f81c9a8e3e5^[[m in
> ^[[33mpygi_marshal_cleanup_args_from_py_marshal_success^[[m (^M
> ^[[36mstate=state@entry^[[m=0x7f81c7137150,
> ^[[36mcache=cache@entry^[[m=0x7f81c00128b0)^M
>
> at ^[[32mgi/pygi-marshal-cleanup.c^[[m:116^M
> #3 ^[[34m0x00007f81c9a8d072^[[m in ^[[33mpygi_invoke_c_callable^[[m (^M
> ^[[36mfunction_cache^[[m=0x7f81c00128b0, ^[[36mstate^[[m=<optimized
> out>, ^M
> ^[[36mpy_args^[[m=<optimized out>, ^[[36mpy_kwargs^[[m=<optimized
> out>) at ^[[32mgi/pygi-invoke.c^[[m:712^M
> #4 ^[[34m0x00007f81c9a8311a^[[m in ^[[33mpygi_function_cache_invoke^[[m
> (^M
> ^[[36mfunction_cache^[[m=<optimized out>,
> ^[[36mpy_args=py_args@entry^[[m=0x7f81c659ae40,
> ^M
> ^[[36mpy_kwargs=py_kwargs@entry^[[m=0x0) at
> ^[[32mgi/pygi-cache.c^[[m:862^M
> #5 ^[[34m0x00007f81c9a8d615^[[m in ^[[33mpygi_callable_info_invoke^[[m
> (^[[36muser_data^[[m=0x0, ^M
> ^[[36mcache^[[m=<optimized out>, ^[[36mkwargs^[[m=0x0,
> ^[[36mpy_args^[[m=0x7f81c659ae40, ^M
>
>
> --
> If something is requisite, how can it possibly be, prerequisite?
>
> vanitas vanitatum omnia vanitas
> later, steve
> http://umn.edu/~barbo
>
>
>
> --
> If something is requisite, how can it possibly be, prerequisite?
>
> vanitas vanitatum omnia vanitas
> later, steve
> http://umn.edu/~barbo
>
>
>
> --
> If something is requisite, how can it possibly be, prerequisite?
>
> vanitas vanitatum omnia vanitas
> later, steve
> http://umn.edu/~barbo
>
>
>
> --
> If something is requisite, how can it possibly be, prerequisite?
>
> vanitas vanitatum omnia vanitas
> later, steve
> http://umn.edu/~barbo
>
>
--
If something is requisite, how can it possibly be, prerequisite?
vanitas vanitatum omnia vanitas
later, steve
http://umn.edu/~barbo
