From: "jiri.horky at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/15101] New: [PATCH] Stap sefaults when calling NSS_shutdown() which was not previously initialized
Date: Tue, 05 Feb 2013 14:21:00 -0000 [thread overview]
Message-ID: <bug-15101-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15101
Bug #: 15101
Summary: [PATCH] Stap sefaults when calling NSS_shutdown()
which was not previously initialized
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: dyninst
AssignedTo: systemtap@sourceware.org
ReportedBy: jiri.horky@gmail.com
Classification: Unclassified
Created attachment 6845
--> http://sourceware.org/bugzilla/attachment.cgi?id=6845
GDB backtrace
Systemtap git version as of 20130105, SLES SP1, 2.6.32.59-0.7.1.du2-default.
Problem: stap segfaults when running probe for NFSD code (see attachment) in
NSS_shutdown(). This is because NSS was previously initiliazed. Please attached
GDB backtrace as an example of such code.
I also include patch that fixes this behavior. The patch was originally written
by my colleague Lukas Hejtmanek.
Jiri Horky
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2013-02-05 14:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 14:21 jiri.horky at gmail dot com [this message]
2013-02-05 14:22 ` [Bug dyninst/15101] " jiri.horky at gmail dot com
2013-02-05 14:23 ` jiri.horky at gmail dot com
2013-02-05 15:09 ` brolley at redhat dot com
2013-02-05 17:19 ` [Bug server/15101] " jistone at redhat dot com
2013-02-06 18:21 ` fche at redhat dot com
2013-02-06 18:23 ` fche at redhat dot com
2013-02-06 21:01 ` fche at redhat dot com
2013-02-06 21:42 ` brolley at redhat dot com
2013-02-06 21:43 ` brolley at redhat dot com
2013-02-07 3:58 ` fche at redhat dot com
2013-02-07 8:19 ` jiri.horky at gmail dot com
2013-02-08 18:13 ` brolley at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15101-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).