Summary: | sys-devel/gdb-6.7.1 bigcore test creates extremly big core file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Kiedrowicz <esqualante> |
Component: | [OLD] Development | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
gdb emerge log
emerge info |
Description
Michał Kiedrowicz
2007-11-06 22:13:09 UTC
Created attachment 135385 [details]
gdb emerge log
Created attachment 135387 [details]
emerge info
it doesnt actually use ~17gb of disk space ... it's created with holes $ stat -c "%b %B %s" core 52440 512 17176354816 that means, on disk, it's only taking up (52440 * 512) bytes (so ~26 megs). the "file size" though is 17gb (In reply to comment #3) First, thank You for looking into this report. However, I get different results: $ stat -c "%b %B %s" gdb.base/bigcore.corefile 33578007 512 17175166976 I'm using reiserfs3.6, but I don't know if it changes anything. It would seem as though the test case is doing what they wanted it to do... yeah, real fix is to get sparse support into the relevant filesystems |