From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/5603] glibc stack-smashing error in staprun on f8 0.6-1 build
Date: Sat, 12 Jan 2008 16:58:00 -0000 [thread overview]
Message-ID: <20080112165743.27124.qmail@sourceware.org> (raw)
In-Reply-To: <20080112153212.5603.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2008-01-12 16:57 -------
Update: am able to reproduce this with CVS systemtap, built with the
same compiler options. valgrind and gdb don't produce any additional
information with this binary, because the stack-smash-detector runs
at the end of the function.
Yet another data point: this message in the kernel logs may relate.
[451468.657609] Systemtap Error at _stp_sym_read_cmd:301 Supplied buffer too
small. count:8192 len:132
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5603
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-01-12 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 15:32 [Bug runtime/5603] New: " fche at redhat dot com
2008-01-12 16:58 ` fche at redhat dot com [this message]
2008-01-12 18:31 ` [Bug runtime/5603] " fche at redhat dot com
2008-01-12 23:06 ` fche at redhat dot com
2008-01-14 15:00 ` hunt at redhat dot com
2008-01-21 17:47 ` fche 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=20080112165743.27124.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).