public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zecke at selfish dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/10717] New: memusagestat SIGFPE and other observations
Date: Thu, 01 Oct 2009 11:03:00 -0000 [thread overview]
Message-ID: <20091001110250.10717.zecke@selfish.org> (raw)
This applie to memusagestat.c of the latest git version. I'm not sure if the usage of memusagestat.c
is supported and if I'm seeing a bug and if patches are welcome.
Using the -T option on a memusage "trace" from an application that was halted and didn't write out
the header entry results in a SIGFPE due "maxsize_total" being 0. If a patch is welcome I would
change the "repair" logic to update maxsize total header entry as well, write the whole headent
structure to disk. And i would move the repair above assigning the maxsize_* variables.
I can upload the data file, my simple test application and a gdb backtrace if that is
required/wanted/wished.
The other observation is that the -t option is not doing anything, from looking at the trace (this is
not from glibc git... but the distro version) is that the time sometimes jump backwards. Does this
classify as opening a new bug?
--
Summary: memusagestat SIGFPE and other observations
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: zecke at selfish dot org
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10717
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2009-10-01 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 11:03 zecke at selfish dot org [this message]
2009-10-29 21:20 ` [Bug libc/10717] " drepper at redhat dot com
2009-10-30 1:47 ` zecke at selfish dot org
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=20091001110250.10717.zecke@selfish.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).