On July 25, 2002 at 15:50 -0400, Dan Espen wrote:
> 
> Usually Purify is good at finding those needles.
> 
> If I knew what Fvwm features you were exercising, I might
> find some time to do a Solaris build and Purify run.
> I need config file statements, and actions to perform.

I am not sure if purify can help here.

Original message: 
  http://www.hpc.uh.edu/fvwm/archive/0207/msg00373.html

The is a memory violation in function paint_menu which is file menus.c
about line 4100. This violation occurs randomly, which doesn't make it
easier ;-), when using  dynamic  menus  together  with  mutliple  menu
styles.  As  far as we found out yet there are two lines in paint_menu
where a voilation occurs. Those two may or may not caused by the  same
problem.  Common is both locations that the pointer sequence mr->s->ms
is accessed. In my last  mail  I  posted  the  values  of  this  three
pointers  shortly  before the crash. The second case I described shows
that the contents of mr->s->ms point to a wrong location. 
The first case I described seems a little bit  odd  to  me  since  the
three pointers seem to have proper values. 

Even I had a look  in  menus.h  where  the  struct  MenuRootStatic  is
described.  In  this  stucture there is a declaration Pixel sideColor;
before  the  declaration  MenuStyle  *ms;.  If  the  pointer  *ms   is
overwritten by accident it may be done by a overflow in this sideColor
variable. To check this one could insert a char array between the  two
declaration  and  watch  this.  If  this is the case the overflow will
affect the char array which otherwise should  be  never  accessed.  If
nothing  comes  out  in  this  case  today  I will probably do this at
weekend. 

Uwe
-- 
+--------------------------------------------------
| Uwe Pross 
|   mailto:[EMAIL PROTECTED]
|   http://www.tu-chemnitz.de/~uwp
+--------------------------------------------------
--
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