About Community / Another Ribosome Index-out-of-range bug? / Ribosome Troubleshooting t

Erick Omar Delgado wrote:
> I am kind of wondering if the developers are upset at
> me or something that I don't get any response/help
> back.  
>   

Hi Erick,

ABOUT COMMUNITY:
If there is any case where nobody responded, it is most
likely that we 
are either too busy with project items, not knowing the
solution off the 
top of our heads, or we simply thought that others would
respond and 
missed it later.

Just like any Open Source project, we desire, more, to see
contribution 
to make the project better -- think of it as the return of
community 
members' hard work. We know that it is harder for us (as in
a limited 
subset of community members) to do it alone.

Cooperation among diverse groups of community members might
not be a 
walk in the park, especially when answers to questions are
not easy to 
find or simply difficult matters to resolve. But still,
people with the 
right ideas, mindset, and skills would bring great and
positive changes. 
Remember that what you don't like, you can change if the
approach is 
right (I don't claim that all changes are easy; but that
they are not 
impossible.)

We would like to see contributing members benefiting from
the projects 
because only then, contributing members would keep coming
back and 
creating a snowball effect that benefits the most of
community members 
and also other users.

We are seriously constrained by available resources and time
to both 
work on project items and supporting questions, so we can
only attempt 
to answer support-questions or request for resources as much
as we can 
and hope participating members would survive the lack of
helpful hands 
in other cases -- think of it as a training to be more
familiar with the 
projects; without problems, you don't discover the inside
working of the 
projects.

> I'm just trying my best to get involve and help
> out and use this wonderful project/product for every
> day use.
>
> Well I deleted everything and started over again and
> the results are the same.  58 out of 132 modules
> failed and the Ribosome Bug is there in the build.out
> file.
>
> Thing is the Helix DNA Client builds fine with no
> errors (besides a few minor problems), but the Helix
> Player does not.  

RIBOSOME BUG:
Now, I do believe that you really ran into a Ribosome bug
that others 
haven't encountered. You were just a bit unlucky... You
should report 
the index-out-of-range error to ribosome-dev mailing list if
you 
haven't. (Yes, I know that there is a bug report already and
that it is 
assigned to the right person.)

https://bugs.helixcommunity.org/show_bug.cgi?id=7187

It can be said that similar thing happened to me as I
pointed out about 
my Ribosome fix. You can do the same if you want.
http://lists.helixcommunity.org/
pipermail/ribosome-dev/2007-February/002014.html

Alternatively, if you were making Release builds, you might
avoid the 
Ribosome bug altogether if you make Debug builds.

RIBOSOME TROUBLESHOOTING TIPS:
If you want to dive into Ribosome, here are a few random
tips from the 
not-very-experienced me (more Ribosome experts in
ribosome-dev mailing 
list); these tips might give you an easier start when
exploring the 
Ribosome code base:

python /usr/lib/python2.4/pdb.py ../../build/bin/build.py
  (1) n
    Start stepping through Python build.py script.
  (2) tool.run()
    At this function, use step:
    s
    Then, next:
    n
  (3) self.__runTool()
  (4) tool.run()
  (5) ShellToolApp().main()
  (6) self.branch_list = branchlist.BranchList(self.cvs_tag,

self.cvs_date, update)
    This Pdb debugger command allows you to see branch
list:
    "p self.branchlist.__dict__"

  (7) PathList.__init__(self, branch_search_path,
"BIF", [ "bif", 
"biif"], tag, timestamp, noupdate)

  (8) chaingang.ChainGang(jobs,3).run()
    Set tbreak at this line and continue execution to this
line.
    Then, step into it.

  (9) return ChainGang_threaded(todo, num)
    Step into this function.
    CHAINGANG_DEBUG environment variable might be useful.

Print Module Names:
(A) Print All BIF Module Names Using Pdb Debugger:
  b build.py:67
    (similar to "break main" gdb breakpoint.)
  c
  b buildapp.py:883
    This is "def checkout_module".

  for module in modules: print module.name
  OUTPUT:
    datatype/rm
    datatype/h263
    datatype/smil
    installer

(B) $BUILD_ROOT/lib/bif.py:
  def start_module(self, attr):
    try:
        outmsg.send("start_module id=%s" %
attr['id'])
    except:
        pass
    try:
        outmsg.send("start_module name=%s" %
attr['name'])
    except:
        pass
    try:
        outmsg.send("start_module type=%s" %
attr['type'])
    except:
        pass
    outmsg.send("")

  OUTPUT:
    start_module id=datatype_dist_rm_audio_renderer
    start_module name=datatype_dist/rm/audio/renderer
    start_module type=name_only

(C) Print Module During Dependency Calculation:
  for module in self.depends.build_list(): print
module.name

(D)
  module_list_to_module_id_list()

(E) Print branchlist:
  p self.branchlist.__dict__

Print To Console From Ribosome Python Scripts:
  outmsg.send("updating file="%s" for
platform="%s"" % (path, 
plat_string))
  Print output to the screen.

Disable Ribosome's Worker Thread For Pdb Debugging:
  $BUILD_ROOT/lib/chaingang.py:
    def ChainGang(todo, num=default_concurrancy):
      #if num>1:
      # return ChainGang_threaded(todo, num)
      return ChainGang_nothreads(todo, num)
  By disabling thread as above, you can set breakpoint in
Pdb to step 
through Ribosome code!

Best of luck in your exploration.

-- 
Daniel Yek.

> I think that maybe there is
> something wrong that needs to be checked carefully in
> the Ribosome cvs tree.
> Below is the error from the first Build System Error
> backwards again.
>
> Build System (V2.4.8)
> time: Thu Aug 30 20:47:02 2007
> outfile: build.out
> branch: hxplay_gtk_current
> platform: linux-2.2-libc6-gcc32-i586
> distribution/archive from: linux-2.2-libc6-gcc32-i586
> build Type: release
> build options: release
> profile:
>
/home/erick/build/umakepf/helix-client-all-defines-free
> <snip>
>   
>   File "/home/erick/build/lib/rlink_exe.py",
line 182,
> in __init__
>     self.parse()
>   File "/home/erick/build/lib/rlink_exe.py",
line 221,
> in parse
>     self.read_sections(data[secstart:secend])
>   File "/home/erick/build/lib/rlink_exe.py",
line 230,
> in read_sections
>     s=Section(w[1], self)
> IndexError: list index out of range
>
-----------------------------------------------------------
>
> I truly wish I knew why I'm having difficulties
> building Helix Player.  I guess it does not like me
> like the client does. lol
>
> Thank you very much for your time and help.
>
> Regards,
> Erick Omar Delgado
>   

_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

About Community / Another Ribosome Index-out-of-range bug? / Ribosome Troubleshooting t

Thread: About Community / Another Ribosome Index-out-of-range bug? / Ribosome Troubleshooting t