From: Simon Strandgaard <0bz63fz3m1qt3001@...>
Date: 2003-04-28T19:40:50+09:00
Subject: Re: c++/ruby debugging advices

On Mon, 28 Apr 2003 09:13:31 +0200, Friedrich Dominicus wrote:

> "Simon Strandgaard" <0bz63fz3m1qt3001@sneakemail.com> writes:
> 
>> Im embedding ruby into c++ and im having a segfault problem which 
>> Im having serious trouble locating.
>> 
>> What really concerns me is that the backtrace (from the coredump) - 
>> it traces back into a part of the application which has nothing to
>> do with ruby. 
>> 
>> Therefore I removed all ruby-code and instead uses some fake-c++ 
>> classes then the bug disapeared.. I guess the problem is ruby.
> That is not very likely. Have you tried to write the FrameWork for
> embedding Ruby? 

mmm.. What do you mean about "framework" ?

 
>> How can I debug this ?
> Well you assume that integrating Ruby is the problem. Than write just
> so much to see how that has to be done.

Yes.. I did that. I made a skeleton project
http://metaeditor.sf.net/embed/


I know ruby is not thread-safe.. but could there be other 
things which I am not aware of ?


I you want to see the code, then you must download 2 tar.gz
files (aeditorlib-0.1.tar.gz & aeditor-qt.tar.gz)
http://sourceforge.net/project/showfiles.php?group_id=41757


backend: The embedding ruby part of the code 
> wc -l *.h *.cpp *.i
901 total

frontend: The application code 
> wc -l */*.cpp */*.h
819 total

You can see my project is still very small (less than 2000 lines of code).
This was suppose to be easy debuggable :-)

--
Simon Strandgaard