[bt-devel] Working BT

[bt-devel@crosswire.org]

Joachim Ansorg writes:

> Hmm, yesterday evening I gor it working and commited to CVS. I think that's why
> it works for you.
> 
> But now I'm sure it's not a source code problem: I compiled and the lines
> apperared. I changed nothing and removed a file from the project file and the
> lines disappeared ! I think it'a problem with linking etc.
> 
> But is this reasonable or possible ??

What did you remove from the project file?  Does adding it back fix the
problem?

If we can find a way to create 2 files that should be identical, except 
that one has this problem, and not the other, perhaps we can compare the
two executables to see what is different.

Just some ideas (kind of like brainstorming):

I haven't checked, but I assume that we are linking the QT and KDE
libraries dynamically, not that I know if this makes a problem more or less
likely...

One guess is that somewhere (either in the compiler, or in the libraries)
there is a problem with alignment of some variable or variables.  Does C++
care about such things as word boundaries on certain data types?  Do the QT
or KDE libraries use assembler, or some other method that could cause a
boundary problem?

By the fact that this one object seems to be the one that has problems, I
would suspect the class library.  However, until we figure out exactly what
causes the problem (perhaps a short program where a single change can make
the problem appear or disappear) it may be hard to give the developers
anything useful to go on.

I know that when I compile QT and/or KDE there are many warnings that come
up.  Perhaps this problem is related to one of these warnings.  As I recall
some of the warnings deal with casting, or inonsistent data types, so there
could be certain features that work or don't work based on otherwise
insignificant changes to our executable.

Do my random thoughts bring any idesa to mind for anyone else?

--
   Darwin Gregory

   Help California define marriage the way God does...
   Support Proposition 22!   Vote YES on Prop 22!