strepsirrhini/office-gobmx
9
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Use "set logging enabled on/off" instead of deprecated "set logging on/off"

Browse source 
With GNU gdb (Debian 13.2-1) 13.2, I noticed this trace on console when using --backtrace

Warning: 'set logging on', an alias for the command 'set logging enabled', is deprecated.
Use 'set logging enabled on'.

Change-Id: Ic03911ea94aff57dee8f594744147302ef01a1ed
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160143
Tested-by: Jenkins
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
This commit is contained in:
Julien Nabet 2023-11-30 11:11:29 +01:00
parent fdbf404073
commit b4ff86cf73
3 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
bin/refcount_leak.py
View file

@ -32,7 +32,7 @@
## II. run test/soffice in gdb and set breakpoints in acquire/release
## with a command to print the backtrace
# set logging on
# set logging enabled on
# break foo.cxx:123
# break foo.cxx:234

4
desktop/scripts/gdbtrace
View file

@ -3,11 +3,11 @@ echo log will be saved as gdbtrace.log, this will take some time, patience...\n
handle SIGPIPE SIGXCPU SIG33 SIG35 SIGPWR nostop noprint
set logging redirect on
set logging file gdbtrace.log
set logging on
set logging enabled on
set logging overwrite on
run
bt
thread apply all bt
quit
set logging off
set logging enabled off
echo log is saved as gdbtrace.log\n

4
solenv/bin/gdbtrycatchtrace
View file

@ -12,10 +12,10 @@ end
echo log will be saved as gdbtrace.log, this will take some time, patience...\n
set logging redirect on
set logging file gdbtrace.log
set logging on
set logging enabled on
set logging overwrite on
run
bt
quit
set logging off
set logging enabled off
echo log is saved as gdbtrace.log\n