diff options
| author | Tom Tromey <tromey@adacore.com> | 2019-06-11 06:59:38 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2019-06-14 07:00:27 -0600 |
| commit | abdb711e0855f0597a96db0486b598144b788212 (patch) | |
| tree | a21b7030c6416a8b0005220652616532f06d3ec8 /gdb/top.c | |
| parent | 9a9e394b05a841bdd9163f280d7ef19cc65634d6 (diff) | |
| download | gdb-abdb711e0855f0597a96db0486b598144b788212.zip gdb-abdb711e0855f0597a96db0486b598144b788212.tar.gz gdb-abdb711e0855f0597a96db0486b598144b788212.tar.bz2 | |
Remove alloca(0) calls
PR gdb/24653 points out that a gcc snapshot will complain about the
calls to alloca(0) in gdb.
These calls are only needed when using the C alloca. I'm inclined to
think that no current platform needs this, so this patch removes the
calls.
Let me know what you think.
gdb/ChangeLog
2019-06-14 Tom Tromey <tromey@adacore.com>
PR gdb/24653:
* regcache.c (registers_changed): Don't call alloca.
* top.c (execute_command): Don't call alloca.
Diffstat (limited to 'gdb/top.c')
| -rw-r--r-- | gdb/top.c | 4 |
1 files changed, 0 insertions, 4 deletions
@@ -560,10 +560,6 @@ execute_command (const char *p, int from_tty) auto cleanup_if_error = make_scope_exit (bpstat_clear_actions); scoped_value_mark cleanup = prepare_execute_command (); - /* Force cleanup of any alloca areas if using C alloca instead of - a builtin alloca. */ - alloca (0); - /* This can happen when command_line_input hits end of file. */ if (p == NULL) { |