On Wed, Jun 19, 2002 at 12:29:39PM +0000, Mikhael Goikhman wrote:
> On 19 Jun 2002 14:33:16 +0200, Dominik Vogt wrote:
> > 
> > On Wed, Jun 19, 2002 at 10:49:55AM +0000, Mikhael Goikhman wrote:
> > > Program terminated with signal 11, Segmentation fault.
> > > 
> > > #0  paint_menu (mr=0x80e2d38, pevent=0x80b8760, fw=0x0) at menus.c:4038
> > > 4038            int bw = MST_BORDER_WIDTH(mr);
> > [snip]
> > 
> > > (gdb) print mr->s->ms
> > > $1 = (MenuStyle *) 0x78696e75
> > > (gdb) print mr->s->ms->look
> > > Cannot access memory at address 0x78696e81
> > > (gdb) 
> > 
> > What about mr and mr->s?  Do they contain useful information?
> > Could you please post the output of
> > 
> >   (gdb) print *mr
> >   (gdb) print *(mr->s)
> >   (gdb) print *(mr->s->ms)
> 
> Since then (15 Jun) this core file was replaced with another one.
> And this new core was replaced with the gnome panel core as well.
> But there is its stack.
> 
> > Can you remember anything you did around the time that the core
> > dump happened?  Modified any menus or menu styles or opened/closed
> > a tear-off menu?
> 
> I do much more than an ordinary user. Especially before a new fvwm-themes
> release, but this is also the reason why I do not remember what exactly I
> did after Restart and what after a theme switching (no Restart).
> It crashed (the first core) when I navigated a non-trivial menu tree.
> 
> The second crash (below) was even before a root menu was poped up.
> 
> I hoped the stack alone was enough.

Well, it crashed with a corrupt menu style structure, but nowhere
near any of the functions that fiddle with the menu styles.  Can
you compile the menu files with efence enabled and see if you get
any new core dumps, please?

> I will print more when I get a core again.

Bye

Dominik ^_^  ^_^

-- 
Dominik Vogt, email: [EMAIL PROTECTED]
LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen
fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20
--
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