NetBSD Problem Report #44829

From martin@duskware.de  Tue Apr  5 21:50:26 2011
Return-Path: <martin@duskware.de>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 858EE63C117
	for <gnats-bugs@gnats.NetBSD.org>; Tue,  5 Apr 2011 21:50:26 +0000 (UTC)
Message-Id: <20110405215026.858EE63C117@www.NetBSD.org>
Date: Tue,  5 Apr 2011 21:50:26 +0000 (UTC)
From: martin@NetBSD.org
Reply-To: martin@NetBSD.org
To: gnats-bugs@gnats.NetBSD.org
Subject: gdb -q prints bogus messages
X-Send-Pr-Version: 3.95

>Number:         44829
>Category:       toolchain
>Synopsis:       gdb -q prints bogus messages
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    toolchain-manager
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Apr 05 21:55:00 +0000 2011
>Closed-Date:    Wed Mar 20 08:35:17 +0000 2013
>Last-Modified:  Wed Mar 20 08:35:17 +0000 2013
>Originator:     Martin Husemann
>Release:        NetBSD 5.99.48
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD night-owl.duskware.de 5.99.48 NetBSD 5.99.48 (NIGHT-OWL) #29: Mon Apr 4 22:12:24 CEST 2011 martin@night-owl.duskware.de:/usr/src/sys/arch/amd64/compile/NIGHT-OWL amd64
Architecture: x86_64
Machine: amd64
>Description:

When invoked wiht -q (quiet, supposed to suppress initial messages) to analyze
a core dump, gdb still prints lots of "no debugging symbols found" messages,
but ommits the shared library file name - so the messages are all totally
meaningless. Example from an atf test run (first line is from atf-run):

Test program crashed; attempting to get stack trace
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Core was generated by `t_pr'.
Program terminated with signal 6, Aborted.
#0  0x00000000417604c4 in abort () from /usr/lib/libc.so.12
#0  0x00000000417604c4 in abort () from /usr/lib/libc.so.12
#1  0x0000000041309d78 in rumpuser_exit () from /usr/lib/librumpuser.so.0
#2  0x00000000411968e8 in rumpns_cpu_reboot () from /usr/lib/librump.so.0
#3  0x00000000411655ec in rumpns_panic () from /usr/lib/librump.so.0
#4  0x0000000040505f08 in rumpns_union_write ()
   from /usr/lib/librumpfs_union.so.0
#5  0x000000004115a720 in rumpns_VOP_WRITE () from /usr/lib/librump.so.0
#6  0x0000000040f2c6ec in rumpns_vn_extattr_get ()
   from /usr/lib/librumpvfs.so.0
...

>How-To-Repeat:
just invoke gdb -q on a core generated by a standard binary from a NetBSD
distribution.

>Fix:
Either suppress the (no debugging symobls found) messages with -q, or don't
suppress the loading file name info. For atf, I would prefer the former
slightly.

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sat, 31 Dec 2011 21:03:57 +0000
State-Changed-Why:
It looks to me like gdb7 improved this... do you think it's good enough?
(it doesn't seem to be very quiet, for example)


State-Changed-From-To: feedback->closed
State-Changed-By: martin@NetBSD.org
State-Changed-When: Wed, 20 Mar 2013 08:35:17 +0000
State-Changed-Why:
Behaviour is now, while not quiet, at least consistent and matches documentation


>Unformatted:

Home	PR Database Search