This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/10717] New: memusagestat SIGFPE and other observations


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]