Fix 325714 Empty vgcore but RLIMIT_CORE is big enough (too big)
Use ULong rather than UInt for coredump file size.
Tested manually by
ulimit -c 4294967296
./vg-in-place ./gdbserver_tests/gone abort
valgrind creates vgcore.xxxxx unusable by GDB.
With the fix, GDB can read the core dump.
Patch from Romain Geissler
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13762 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/NEWS b/NEWS
index 6e484ef..fa4537c 100644
--- a/NEWS
+++ b/NEWS
@@ -13,8 +13,8 @@
* New and modified GDB server monitor features:
- - A new monitor command "v.info stats" that shows various valgrind core and tool
- statistics.
+ - A new monitor command "v.info stats" that shows various valgrind core and
+ tool statistics.
* ==================== FIXED BUGS ====================
@@ -29,6 +29,7 @@
https://bugs.kde.org/show_bug.cgi?id=XXXXXX
where XXXXXX is the bug number as listed below.
+325714 Empty vgcore but RLIMIT_CORE is big enough (too big)
326462 Refactor vgdb to isolate invoker stuff into separate module
326983 Clear direction flag after tests on amd64.
327238 Callgrind Assertion 'passed <= last_bb->cjmp_count' failed