e7db4ec014
* ptype/o prints offsets and sizes of members (like pahole)
* tab-completion improved: quoting function names is not generally
necessary anymore, completion offers for breakpoint don't include
data symbol
* enable/disable breakpoints now accept ranges: 'disable 1.3-5'
* new commands:
- set/show cwd: working directory of debuggee
- set/show compile-gcc: program to use for 'compile' command
- starti: start program and stop at first instruction
- TUI single-key commands: 'i' for stepi and 'o' for nexti
* --readnever option disables any reading of debug info (for dumping)
* s390: guarded storage register access for z14
* gcore option -a dumps all memory mapping
* C++ breakpoints: 'b foo' will now set a breakpoint on all functions
and methods named 'foo' no matter the scope. Use -qualified if you
don't want that
* python scripting: new events gdb.new_inferior, gdb.inferior_deleted
and gdb.new_thread; new command rbreak (breakpoint accepting regexps)
* gdbserver can be passed environment parameters to remote debuggee
- Added patches from Fedora:
gdb-ppc64-stwux-tautological-compare.patch
gdb-rhbz1540559-gdbaddindex-glibcdebug-regression.patch
gdb-vla-intel-fix-print-char-array.patch
- Removed unused gdb-libstdc++-v3-python-7.1.1-20170526.tar.bz2
- Removed obsolete upstream patches:
gdb-s390x-1b63490.patch
gdb-s390x-289e23a.patch
gdb-s390x-8fe09d7.patch
gdb-s390x-96235dc.patch
OBS-URL: https://build.opensuse.org/package/show/devel:gcc/gdb?expand=0&rev=177
81 lines
2.3 KiB
Diff
81 lines
2.3 KiB
Diff
From FEDORA_PATCHES Mon Sep 17 00:00:00 2001
|
|
From: Fedora GDB patches <invalid@email.com>
|
|
Date: Fri, 27 Oct 2017 21:07:50 +0200
|
|
Subject: nomem: internal_error -> error
|
|
|
|
FileName: gdb-bz568248-oom-is-error.patch
|
|
|
|
;; Out of memory is just an error, not fatal (uninitialized VLS vars, BZ 568248).
|
|
;;=push+jan: Inferior objects should be read in parts, then this patch gets obsoleted.
|
|
|
|
http://sourceware.org/ml/gdb-patches/2010-06/msg00005.html
|
|
|
|
Hi,
|
|
|
|
unfortunately I see this problem reproducible only with the
|
|
archer-jankratochvil-vla branch (VLA = Variable Length Arrays - char[var]).
|
|
OTOH this branch I hopefully submit in some form for FSF GDB later.
|
|
|
|
In this case (a general problem but tested for example on Fedora 13 i686):
|
|
|
|
int
|
|
main (int argc, char **argv)
|
|
{
|
|
char a[argc];
|
|
return a[0];
|
|
}
|
|
|
|
(gdb) start
|
|
(gdb) print a
|
|
../../gdb/utils.c:1251: internal-error: virtual memory exhausted: can't allocate 4294951689 bytes.
|
|
|
|
It is apparently because boundary for the variable `a' is not initialized
|
|
there. Users notice it due to Eclipse-CDT trying to automatically display all
|
|
the local variables on each step.
|
|
|
|
Apparentl no regressions on {x86_64,x86_64-m32,i686}-fedora13-linux-gnu.
|
|
But is anone aware of the reasons to use internal_error there?
|
|
I find simple error as a perfectly reasonable there.
|
|
(history only tracks it since the initial import)
|
|
|
|
IIRC this idea has been discussed with Tom Tromey, not sure of its origin.
|
|
|
|
I understand it may be offtopic for FSF GDB but from some GDB crashes I am not
|
|
sure if it can happen only due to the VLA variables.
|
|
|
|
Thanks,
|
|
Jan
|
|
|
|
gdb/
|
|
2010-06-01 Jan Kratochvil <jan.kratochvil@redhat.com>
|
|
Tom Tromey <tromey@redhat.com>
|
|
|
|
* utils.c (nomem): Change internal_error to error.
|
|
---
|
|
gdb/utils.c | 6 ++----
|
|
1 file changed, 2 insertions(+), 4 deletions(-)
|
|
|
|
diff --git a/gdb/utils.c b/gdb/utils.c
|
|
index c531748fe4..0066bfcc4b 100644
|
|
--- a/gdb/utils.c
|
|
+++ b/gdb/utils.c
|
|
@@ -774,13 +774,11 @@ malloc_failure (long size)
|
|
{
|
|
if (size > 0)
|
|
{
|
|
- internal_error (__FILE__, __LINE__,
|
|
- _("virtual memory exhausted: can't allocate %ld bytes."),
|
|
- size);
|
|
+ error (_("virtual memory exhausted: can't allocate %ld bytes."), size);
|
|
}
|
|
else
|
|
{
|
|
- internal_error (__FILE__, __LINE__, _("virtual memory exhausted."));
|
|
+ error (_("virtual memory exhausted."));
|
|
}
|
|
}
|
|
|
|
--
|
|
2.14.3
|
|
|