Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 198299 - sys-devel/gdb-6.7.1 bigcore test creates extremly big core file
Summary: sys-devel/gdb-6.7.1 bigcore test creates extremly big core file
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Toolchain Maintainers
Depends on:
Reported: 2007-11-06 22:13 UTC by Michał Kiedrowicz
Modified: 2009-04-29 21:43 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

gdb emerge log (gdb-log,282.23 KB, text/plain)
2007-11-06 22:13 UTC, Michał Kiedrowicz
emerge info (,3.15 KB, text/plain)
2007-11-06 22:15 UTC, Michał Kiedrowicz

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Kiedrowicz 2007-11-06 22:13:09 UTC
bigcore test creates huge core file and stops only because it is timed out. gdb fails also other tests, but this one causes more problems - it uses 17GB of disk space (!).

du gdb-6.7.1/gdb/testsuite/gdb.base/bigcore.corefile 
16784876	gdb-6.7.1/work/gdb-6.7.1/gdb/testsuite/gdb.base/bigcore.corefile

Creation of so big file may be connected with my ulimit settings, but this test should check them.

$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 8120
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 8120
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

Reproducible: Always
Comment 1 Michał Kiedrowicz 2007-11-06 22:13:54 UTC
Created attachment 135385 [details]
gdb emerge log
Comment 2 Michał Kiedrowicz 2007-11-06 22:15:09 UTC
Created attachment 135387 [details]
emerge info
Comment 3 SpanKY gentoo-dev 2008-02-25 01:18:06 UTC
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
Comment 4 Michał Kiedrowicz 2008-02-25 14:47:22 UTC
(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.
Comment 5 Mark Loeser (RETIRED) gentoo-dev 2009-04-20 17:52:37 UTC
It would seem as though the test case is doing what they wanted it to do...
Comment 6 SpanKY gentoo-dev 2009-04-29 21:43:29 UTC
yeah, real fix is to get sparse support into the relevant filesystems