Previously...
>I must be jinxed...
>Performing the same chages listed below, and substituting for the sound
>playing program as
>
>AddToFunc "myplay" "I" Exec exec /usr/local/bin/play /usr/share/sound/$0
>
>I've also tried substituting wavplay (the sound files are .wav files) with
>the same result.
>
>I still get a core dump. What's worse, the FvwmEvent man pages suggest
>simple examles of using FvwmEvent, like echo-ing a string to the terminal.
>Even this simple example from the man pages causes a core dump for me. Is
>it possible I'm missing something big? or even little... I should say
>that I'm trying this with fvwm2.2.046 and fvwm2.2.2
It dumps core with 2.0.46 and with 2.2.2? My first suspicion is to ask
you what your ModulePath is defined as in .fvwm2rc. Note that the
behavior of the builtin ModulePath changed between 2.0 and 2.2. It's a
bit odd that 2.0.46's Event is coring, but maybe there's a third
version of Event that's causing trouble... To sum up, make sure that
you're not trying to run the wrong version of Event, since it makes a
distinct difference... not necessarily between 2.2 and 2.3, but
definitely between 2.0 and 2.2.
Other than that, you could always do the following:
1) Figure out which FvwmEvent you think you're running
2) do a 'gdb $fvwmeventpath'
3) in gdb, 'core core' (assuming you're in the directory containing
the FvwmEvent core)
4) 'where'
5) catch that output and send it to the bug tracking system or to
fvwm-workers_at_fvwm.org
--
mikehan_at_best.com
I will return the seeing-eye dog
- The collected wisdom of Bart Simpson
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Jun 09 1999 - 14:22:44 BST