aboutsummaryrefslogtreecommitdiff
path: root/gdb/infcmd.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2022-11-26 14:29:10 +0100
committerTom de Vries <tdevries@suse.de>2022-11-26 14:29:10 +0100
commit7a0daa48da726f9c05a752e85fefe128bf848916 (patch)
tree9dd4b85792e6f028fc967f58bc37707ded3ae80a /gdb/infcmd.c
parent05ad0d60341f0933501dc90002da3d4594c30438 (diff)
downloadgdb-7a0daa48da726f9c05a752e85fefe128bf848916.zip
gdb-7a0daa48da726f9c05a752e85fefe128bf848916.tar.gz
gdb-7a0daa48da726f9c05a752e85fefe128bf848916.tar.bz2
[gdb/testsuite] Don't generate core in gdb.base/bt-on-fatal-signal.exp
When running test-case gdb.base/bt-on-fatal-signal.exp on powerpc64le-linux I noticed: ... FAIL: gdb.base/bt-on-fatal-signal.exp: SEGV: scan for backtrace (timeout) ... The timeout is 10 seconds, but generating the core file takes more than a minute, probably due to slow NFS. I managed to reproduce this behaviour independently of gdb, by compiling "int main (void) { __builtin_abort (); }" and running it, which took 1.5 seconds for a core file 50 times smaller than the one for gdb. Fix this by preventing the core file from being generated, using a wrapper around gdb that does "ulimit -c 0". Tested on x86_64-linux.
Diffstat (limited to 'gdb/infcmd.c')
0 files changed, 0 insertions, 0 deletions