Re: *FvwmEvent: toggle_paging metal.au causes FvwmEvent to crash

2009-07-08 Thread Viktor Griph
2009/6/30 Manoj Srivastava sriva...@acm.org:
 Hi,

        This was reported by a Debian use. Please retain the CC to
        438132-forwar...@bugs.debian.org so that the Dewbian BTS has a
        copy of your contribution.

        I have not been able to reproduce this crash, but I am passing
  it along in case  someone here has a better view into this.

        Originally reported for version 2.5.21; and most recently
  reconfirmed for version: 2.5.23 and 2.5.25.


 --8---cut here---start-8---
 EvwmEvent segfaults every time. I get this in my dmesg:

 FvwmEvent[3014]: segfault at  rip 2af1873cfcdc rsp 
 7fff240ad048 error 4

 I found out that if the following line exists in my config-file,
 FvwmEvent seg-faults at startup:

 *FvwmEvent: toggle_paging metal.au

 Also, after trying several modifications to the config-file, both
 FvwmEvent and fvwm seg-faults very easily. The config-file parser
 seems to be broken, at least on amd64.

I've committed a fix for this to CVS. The introduction of a new module
message in 2.5.19 made the event table off by one for the trailing
events (breaking startup, shutdown and unknown), and if a config name
didn't match a known event would cause deference of a uninitialized
static array element. (gcc sets them to null)

The patch is one line, but is just as unrouboust as before, and will
break again with the introduction of new Module messages. A proper
patch would change the handling of the module messages to skip
messages not dealt with in the module.

/Viktor



*FvwmEvent: toggle_paging metal.au causes FvwmEvent to crash

2009-06-30 Thread Manoj Srivastava
Hi,

This was reported by a Debian use. Please retain the CC to
438132-forwar...@bugs.debian.org so that the Dewbian BTS has a
copy of your contribution.

I have not been able to reproduce this crash, but I am passing
 it along in case  someone here has a better view into this.

Originally reported for version 2.5.21; and most recently
 reconfirmed for version: 2.5.23 and 2.5.25.


--8---cut here---start-8---
EvwmEvent segfaults every time. I get this in my dmesg:

FvwmEvent[3014]: segfault at  rip 2af1873cfcdc rsp 
7fff240ad048 error 4

I found out that if the following line exists in my config-file,
FvwmEvent seg-faults at startup:

*FvwmEvent: toggle_paging metal.au

Also, after trying several modifications to the config-file, both
FvwmEvent and fvwm seg-faults very easily. The config-file parser
seems to be broken, at least on amd64.
--8---cut here---end---8---

I have never been able to reproduce this for any version.

manoj
-- 
I don't like spinach, and I'm glad I don't, because if I liked it I'd
eat it, and I just hate it. -- Clarence Darrow
Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C



Re: *FvwmEvent: toggle_paging metal.au causes FvwmEvent to crash

2009-06-30 Thread Thomas Adam
2009/6/30 Manoj Srivastava sriva...@acm.org:
 Hi,

        This was reported by a Debian use. Please retain the CC to
        438132-forwar...@bugs.debian.org so that the Dewbian BTS has a
        copy of your contribution.

        I have not been able to reproduce this crash, but I am passing
  it along in case  someone here has a better view into this.

        Originally reported for version 2.5.21; and most recently
  reconfirmed for version: 2.5.23 and 2.5.25.


 --8---cut here---start-8---
 EvwmEvent segfaults every time. I get this in my dmesg:

 FvwmEvent[3014]: segfault at  rip 2af1873cfcdc rsp 
 7fff240ad048 error 4

OK, so that's memory-related then.  :P

 I found out that if the following line exists in my config-file,
 FvwmEvent seg-faults at startup:

 *FvwmEvent: toggle_paging metal.au

Was this linked using librplay, out if interest?

 Also, after trying several modifications to the config-file, both
 FvwmEvent and fvwm seg-faults very easily. The config-file parser
 seems to be broken, at least on amd64.

That's a rather bold statement to make about the config-file parser (I
wasn't aware we had one per se.  :P).I wasn't able to reproduce
this either when I looked into it a while back.  Unless the reporter
can obtain a corefile, and hence a backtrace, there's not a lot to be
done.

-- Thomas Adam