[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb-bugs
Subject:    Assertion failed
From:       "Wilhelm Pastoors/Denic" <pastoors () denic ! de>
Date:       2002-11-07 13:28:16
Message-ID: OF35DA8E92.8F50A36C-ONC1256C6A.0047C00F-C1256C6A.004A0015 () denic ! de
[Download RAW message or body]


error txt:

"
(gdb) bt
ui-out.c:133: gdb-internal-error: push_level: Assertion `uiout->level >= 0
&& uiout->level < MAX_UI_OUT_LEVELS' failed.
An internal GDB error was detected.  This may make further
debugging unreliable.  Quit this debugging session? (y or n) y
"

gdb was called as: "gdb w5Talk core"
You will find more information in the gdb_bug - file,
which is attached.
I saved the core file; if you like to get it, let me
know (it has as much as 17071120 bytes) and I will send it.

I was hunting the following bug:
"
Assertion failed: m_monitor_owner == NULL, file SysMonitor_md.cpp, line 302
Abort (core dumped)
"
which occures in 1 of a 100 runs on my machine.
If I knew how to compile gdb not to crash on SunOS 5.9
with an assertion error I also knew how to compile my program
that way :-)

Additional information:

gdb --version:

GNU gdb 5.2.1
....
This GDB was configured as "sparc-sun-solaris2.9".


uname -a:

SunOS denics4 5.9 Generic_112233-02 sun4u sparc SUNW,Ultra-Enterprise


gdb was compiled with ./configure without setting further options.
The compiler used was probably gcc 3.2 (sys adm wasn't sure, can be
it was gcc 3.1).


Sincerely

Wilhelm Pastoors


(See attached file: gdb_bug)

["gdb_bug" (application/octet-stream)]

[prev in list] [next in list] [prev in thread] [next in thread]