Re: Crashes with binaries compiled from source

[Johannes Kroll <j-kroll gmx de>]

On Tue, 2006-02-07 at 20:44 +0100, Murray Cumming wrote:
> On Tue, 2006-02-07 at 20:05 +0100, Johannes Kroll wrote:
> > On Tue, 2006-02-07 at 17:48 +0100, Murray Cumming wrote:
> > > On Sat, 2006-02-04 at 11:30 +0100, Murray Cumming wrote:
> > > > On Fri, 2006-02-03 at 17:48 +0100, Johannes Kroll wrote:
> > > [snip]
> > > > > I think I will compile on a fresh Ubuntu install on VMWare next, and see
> > > > > if I still get the errors there.  
> > > >
> > > > Please make sure that you use the default compiler. Various versions of
> > > > g++ are not ABI compatible. And please make a note of what dependent
> > > > packages you build from source instead of using from Ubuntu's regular
> > > > repositories.
> > >
> > > If you still see the problem (or in general) I would really like to see
> > > a bugzilla report, ideally with a gdb backtrace. I want to make Glom
> > > absolutely rock solid, but I need actual problems to solve.
> >
> > I'm still trying to find out what this could be... After your suggestion
> > about C++ ABI incompatibility I wrote a little perl script that walks
> > all dependent libraries of an ELF file and looks at version info. Maybe
> > it's useful to you too, so I attached it. However they all seem to use 
> > C++ ABI 1.3 (if any), so that doesn't seem to be the problem.
>
> I doubt that there's any definitive test for this kind of thing. But I'd
> still like to see that bugzilla report with that backtrace, along with
> other details that you've mentioned already.

I'll do the bugzilla report. But because I use Debian repositories as
well as Ubuntu, and also compiled some packages from source previously,
finding out which packages come from what source is quite hard. So I
thought if we compared library versions etc. from that script we might
find out something. 

If noone else can reproduce the bug it might as well be a configuration
problem on my machine. I just hope I'll get it to work soon so I can
start working on the relationships overview.

> > > Also, what locale are you using? In the past, some locales have had
> > > translated markup that has caused problems.
> >
> > Looks like I'm using "C":
> > ~> locale
> > LANG=C
> > LC_CTYPE="C"
> > LC_NUMERIC="C"
> > LC_TIME="C"
> > LC_COLLATE="C"
> > LC_MONETARY="C"
> > LC_MESSAGES="C"
> > LC_PAPER="C"
> > LC_NAME="C"
> > LC_ADDRESS="C"
> > LC_TELEPHONE="C"
> > LC_MEASUREMENT="C"
> > LC_IDENTIFICATION="C"
> > LC_ALL=
>
> OK, so this is unlikely to be the problem.
>
> > I remember setting the locale back to "default" because the german
> > translations of many programs were so bad.
>
> Like anything, you'll have to report that to get it fixed. The
> translators are responsive.