xfce4-panel on Solaris/BrokenWindows: BadAlloc error

[Mike Russo]

On Wed, 2003-07-23 at 17:27, Olivier Fourdan wrote:

I loaded up xfce4-panel in gdb, but I can't do a backtrace because
xfce4-panel exits. So I set a breakpoint on load_plugin() having nowhere
else to start, and single-stepped through, doing a backtrace right after
the "separator" module loads (the last one that loads sucessfully).
After that, of course, it crashes... is there a better way to get more
info? Or does Xsun just suck royally (actually I already know it does).


from gdb:

Breakpoint 1, 0x169a8 in load_plugin ()
(gdb) n
Single stepping until exit from function load_plugin, 
which has no line number information.
** Message: xfce4-panel: module systembuttons successfully loaded
0x16738 in add_plugin_classes ()
(gdb) n
Single stepping until exit from function add_plugin_classes, 
which has no line number information.

Breakpoint 1, 0x169a8 in load_plugin ()
(gdb) n
Single stepping until exit from function load_plugin, 
which has no line number information.
** Message: xfce4-panel: module pager successfully loaded
0x16738 in add_plugin_classes ()
(gdb) s
Single stepping until exit from function add_plugin_classes, 
which has no line number information.

Breakpoint 1, 0x169a8 in load_plugin ()
(gdb) s
Single stepping until exit from function load_plugin, 
which has no line number information.
** Message: xfce4-panel: module separator successfully loaded
0x16738 in add_plugin_classes ()
(gdb) backtrace
#0  0x16738 in add_plugin_classes ()
#1  0x1c540 in create_panel ()
#2  0x1be10 in main ()
(gdb) s
Single stepping until exit from function add_plugin_classes, 
which has no line number information.
The program 'xfce4-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 204 error_code 11 request_code 131 minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
function.)

Program exited with code 01.


Don't worry too much about it, because the xfce3 panel still works
great, and the 4.x panel works with the Xvnc server. Here's my current
config, in case someone else out there on the list has the same setup:

SPARCstation 20 w/ 4MB VSIMM/SX/CG14 framebuffer
Solaris 8 w/ latest recommended patchkit (but older CG14 driver -- the
	newer ones cause Xsun to leak memory at an astounding rate)
running in 24-bit mode
compiled XFce4 with gcc 3.2.2

thanks guys!


> Mike,
> 
> Do what is said in the message:
> 
> xfce4-panel --sync
> 
> and then try the same from gdb (or any other debugger)
> 
> JAsper, it's an X error, not a regular crash... Means that even the
> degugger might not see anything wrong here...
> 
> Cheers,
> Olivier.
> 
> On Wed, 2003-07-23 at 23:07, Jasper Huijsmans wrote:
> > Hey Mike,
> > 
> > I honestly have no clue what is causing this. Perhaps you can try
> > getting a gdb backtrace?
> > 
> > 	Jasper
> > 
> > 
> > On 23 Jul 2003 16:50:29 -0400
> > Mike Russo <miker at readq.com> wrote:
> > 
> > > Hello All! I've been a happy user of XFce since 3.8.11, it has
> > > lengthened the life of my little sparcstation 20. of course i still
> > > want to push it, so I've been trying out XFce 4 betas, and have gotten
> > > everything to compile and work except xfce4-panel... when I run it, I
> > > get the message:
> > > [miker at hamlin miker]$ xfce4-panel                             
> > > ** Message: xfce4-panel: Running without session manager
> > > ** Message: xfce4-panel: module clock successfully loaded
> > > ** Message: xfce4-panel: module mailcheck successfully loaded
> > > ** Message: xfce4-panel: module switcher successfully loaded
> > > ** Message: xfce4-panel: module systembuttons successfully loaded
> > > ** Message: xfce4-panel: module pager successfully loaded
> > > ** Message: xfce4-panel: module separator successfully loaded
> > > The program 'xfce4-panel' received an X Window System error.
> > > This probably reflects a bug in the program.
> > > The error was 'BadAlloc (insufficient resources for operation)'.
> > >   (Details: serial 117 error_code 11 request_code 131 minor_code 5)
> > >   (Note to programmers: normally, X errors are reported
> > >   asynchronously;
> > >    that is, you will receive the error a while after causing it.
> > >    To debug your program, run it with the --sync command line
> > >    option to change this behavior. You can then get a meaningful
> > >    backtrace from your debugger if you break on the gdk_x_error()
> > > function.)
> > > 
> > > xfwm4 and all the other XFce4 components load fine, and work well. If
> > > you'd like me to do any type of testing, straceing, or debugging, let
> > > me know. So far I know that if I set up an Xvnc server on the same
> > > machine, all the XFce4 components (including the panel) run fine. 
> > > 
> > >  Russo <miker at readq.com>
> > > ReadQ Systems, Inc.
> > > 
> > > _______________________________________________
> > > Xfce4-dev mailing list
> > > Xfce4-dev at xfce.org
> > > http://moongroup.com/mailman/listinfo/xfce4-dev
> > 
> > 
> > _______________________________________________
> > Xfce4-dev mailing list
> > Xfce4-dev at xfce.org
> > http://moongroup.com/mailman/listinfo/xfce4-dev
-- 
Mike Russo <miker at readq.com>
ReadQ Systems, Inc.