aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-08-22 09:49:53 +0200
committerTom de Vries <tdevries@suse.de>2024-08-22 09:49:53 +0200
commit78125417227bd3f3765ba52d04066f8607d62f44 (patch)
tree5b7614ca832a383608fc0ecaff8d62de74196083
parenta16c032a5c67453e88bc58dc3db0ac568c348973 (diff)
downloadbinutils-78125417227bd3f3765ba52d04066f8607d62f44.zip
binutils-78125417227bd3f3765ba52d04066f8607d62f44.tar.gz
binutils-78125417227bd3f3765ba52d04066f8607d62f44.tar.bz2
[gdb] Add & in catch in svr4_handle_solib_event
In svr4_handle_solib_event I noticed: ... catch (const gdb_exception_error) ... This seems to be the only place were we do this, elsewhere we have: ... catch (const gdb_exception_error &) ... I suppose the intent of adding '&' is to avoid a copy. I'm not sure if it's necessary given that it's an unnamed const parameter, but I suppose it can't hurt either. Add the '&' here as well. Tested on x86_64-linux. Approved-By: Tom Tromey <tom@tromey.com>
-rw-r--r--gdb/solib-svr4.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/solib-svr4.c b/gdb/solib-svr4.c
index 1a0e542..ff5887a 100644
--- a/gdb/solib-svr4.c
+++ b/gdb/solib-svr4.c
@@ -1948,7 +1948,7 @@ svr4_handle_solib_event (void)
{
link_map_id_val = pa->prob->evaluate_argument (0, frame);
}
- catch (const gdb_exception_error)
+ catch (const gdb_exception_error &)
{
link_map_id_val = NULL;
}