This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/13635] New: Way to reduce warning messages floating in log
- From: "mac-fly at gmx dot net" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 30 Jan 2012 23:18:17 +0000
- Subject: [Bug gdb/13635] New: Way to reduce warning messages floating in log
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13635
Bug #: 13635
Summary: Way to reduce warning messages floating in log
Product: gdb
Version: 7.3
Status: NEW
Severity: normal
Priority: P2
Component: gdb
AssignedTo: unassigned@sourceware.org
ReportedBy: mac-fly@gmx.net
Classification: Unclassified
Environment: Windows XP/7, TDM GCC 4.6.1 / GNU gdb 7.3 for MinGW.
I have compiled Code::Blocks (http://www.codeblocks.org) against wxWidgets
2.9.3 (http://www.wxwidgets.org) and try to debug into a crash. Unfortunately
it is hard to read the log because tons of warning messages like the following:
warning: ../../src/common/menucmn.cpp(976): assert "item" failed in Enable():
attempt to enable an item which doesn't exist
...are floated into the debug log. I know, that is a bug in C::B, but thats
what I am after. I have described the issue here:
http://forums.codeblocks.org/index.php/topic,10908.msg106860.html#msg106860
...and here:
http://forums.codeblocks.org/index.php/topic,10908.msg106928.html#msg106928
A "solution" suggested here:
http://forums.codeblocks.org/index.php/topic,10908.msg106878.html#msg106878
is to filter the warnings by a certain string in the message. While this is an
option, I was told here:
http://forums.codeblocks.org/index.php/topic,10908.msg106933.html#msg106933
...to file a bug report into this bugzilla database to ask if there is a better
way to do it or maybe a feature request to GDB that allows filtering such on
GDB level.
Is that possible / feasible?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.