On Mon, Jul 08, 2002 at 12:17:27PM +0100, Rob Costello wrote:
> hi, Dominik
> 
> Yes, I ran make install....
> 
> fvwm-config -i reports:
> 
> Package: fvwm
> Version: 2.5.2
> 
> Instalation options:
>       prefix: /usr/local
>       exec-prefix: /usr/local
>       bindir: /usr/local/bin
>       datadir: /usr/local/share
>       libexecdir: /usr/local/libexec
>       sysconfdir: /usr/local/etc
>       mandir: /usr/local/man
> 
> Compiled-in paths:
>       Module directory: /usr/local/libexec/fvwm/2.5.2
>       Data directory: /usr/local/share/fvwm
>       Perl lib directory: /usr/local/share/fvwm/perllib
>       Default ImagePath: /usr/include/X11/bitmaps:/usr/include/X11/pixmaps
>       Default UserDir: $HOME/.fvwm

Aha!  As I said, you're having a path problem.  You installed to
/usr/local, but when you ran gdb it used
/opt/fvwm/fvwm-2.5.2/fvwm/fvwm.  I repeat:  are you *sure* that
/usr/local/bin/fvwm is run and not /opt/fvwm/fvwm-2.5.2/fvwm/fvwm?

> On Fri, 2002-07-05 at 16:57, Dominik Vogt wrote:
>     On Fri, Jul 05, 2002 at 02:56:09PM +0100, Rob Costello wrote:
>     > I have not stripped the executable.
>     > 
>     > If I compile without --enable-debug-msgs, fvwm compiles successfully.
>     > 
>     > I have tried disabling and enabling all the extra features with no
>     > success.
>     > 
>     > I ran the test_options script at level 0 - no errors were reported...
>     >
>     > I tried running fvwm -debug, but it core dumped before outputting any
>     > debug info.
>     
>     Forget about the debug stuff in the distribution.  It's not
>     helpful for anything else but running a few sanify checks before a
>     release.
>     
>     Did you install the new fvwm with
>     
>       $ make install
>     
>     ?  Are you sure the correct executable is being executed?  It it
>     in your shell PATH?  If you compiled with just "make", the
>     executable *has* debug information.  When gdb does not display any
>     useful information that means that either the executable that was
>     run has no debug info or gdb did not find the sources.
>     
>     > As a background, I searched for the memory location error in google, and
>     > found a similar bug report (unresolved) on the Flight Gear mailing
>     > list...

Bye

Dominik ^_^  ^_^

 --
Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382
Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe

--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to