[Gambas-user] Problems with OpenSuSE 11 and gcc 4.3

[Benoit Minisini]

On mercredi 30 juillet 2008, Steven Lobbezoo wrote:
> Le mercredi 30 juillet 2008 à 13:42 +0200, Benoit Minisini a écrit :
> > On mercredi 30 juillet 2008, Benoit Minisini wrote:
> > > On mercredi 30 juillet 2008, Steven Lobbezoo wrote:
> > > > Le mercredi 30 juillet 2008 à 13:30 +0200, Benoit Minisini a écrit :
> > > > > On mercredi 30 juillet 2008, Steven Lobbezoo wrote:
> > > > > > Sorry again Benoit,
> > > > > >
> > > > > > Now I got it right, here's the console :
> > > > > > ...
> > > > >
> > > > > Why is gbx2 not compiled with debugging information?
> > > >
> > > > ???????????????
> > > >
> > > > > What do you get if you type 'gbx2 -V'?
> > > >
> > > > 2.8.0
> > >
> > > And if you type 'gbx2 -h'?
> >
> > Sorry, you must first update your local repository to the revision 1487!
>
> Ok, I re-installed completely 1487 (clean install)
> It gives me :
>
> steven at ...1948...:~/2.0/app/src/gambas2> gbx2 -h
>
> GAMBAS Interpreter version 2.8.0 Jul 30 2008 14:22:02
> Compiled with gcc 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision
> 135036]
> (c) 2000-2007 Benoit Minisini
>
> This program is free software; you can redistribute it and/or
> modify it under the terms of the GNU General Public License as
> published by the Free Software Foundation; either version 2, or
> (at your option) any later version.
>
> Usage: gbx2 [options] [<project file>] -- ...
>        gbx2 -e <expression>
>
> Options:
>   -V --version   display version
>   -h --help      display this help
>   -e             evaluate an expression
>   -g             enter debugging mode
>   -p             disable preloading
>   -k             do not unload shared libraries
>   -x             execute an archive
>
> steven at ...1948...:~/2.0/app/src/gambas2>
>
>
> Steven
>

OK. That's the right version. Are you sure that you didn't remove debugging 
information when recompiling? They are activated by default, so it should be 
ok.

Now launch valgrind again, and send me the result. If the debugging 
information are present in the gbx2 executable, you will see function names 
and line numbers in valgrind backtrace, not just the name of the executable.

Regards,

-- 
Benoit Minisini