Re: [Discuss-gnuradio] Gnu Radio Companion (GRC) 0.69 experience

[Berndt Josef Wulf]

G'day,

Still crashes here with the following error messages:

No module named serial  in RS232 Source! -> continuing...
No module named serial  in RS232 Sink! -> continuing...
Removing empty category "Custom"...
>>> Verbose:
Traceback (most recent call last):
  File "/home/wulf/projects/gnuradio/grc/src/ExecFlowGraphGUI.py", line 248, 
in ?
    exit(0)
TypeError: 'str' object is not callable

>>> Done
The program 'Editor.py' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length 
erro'.
  (Details: serial 10975 error_code 16 request_code 151 minor_code 23)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


cheerio Berndt 

On Saturday 19 January 2008 05:38:46 Josh Blum wrote:
> The error seems to come from gtk.main and not from the GRC source
> itself. Perhaps this is the result of a race condition (in grc) between
> the the main thread and the thread waiting on the flow graph to finish.
>
> ->By clicking the kill button, the waiting thread finishes by calling
> the very same method that handles the "kill button" press. Perhaps in
> all the ruckus, some gtk functions get called by 2 threads at once, and
> eventually gtk gets upset and dies/crashes...
>
> I committed a fix for this in the GRC trunk. Can somebody with this
> issue try out the trunk fix and let me know?
>
> -Josh
>
> Ed Criscuolo wrote:
> > I've seen this exact same behavior for some time.  I'm currently
> > running the latest GnuRadio release and GRC 0.69 on Mac OSX 10.4.11
> >
> > @(^.^)@  Ed
> >
> > Achilleas Anastasopoulos wrote:
> >> I would like to thank again Josh for the wonderfull job on GRC:
> >> I am now using it regularly  for my classroom demonstrations on
> >> analog/digital communications.
> >>
> >> I have noticed (it has been more than 6 months since the last time I
> >> used it) that 0.69 version crashes a lot with my fedora 7 (64 bit).
> >> In fact, 8 out of 10 times that I stop a running graph (usually with
> >> 4-5 graphical sinks running) either by closing the graph window or by
> >> pressing the "stop" button on the graphical editor of GRC, it closes
> >> the entire GRC editor...
> >>
> >> Can someone confirm this behavior?
> >>
> >> Thanks
> >> Achilleas