How to perform memory growth analysis using debugger?

[Mikhail_L]

I try to perform analysis with "Select analysis start with debugger" using Intel Inspector 2021.4 on Ubuntu 18.04 host.

It starts with the message

Stopped at target entry
 - waiting for debugger to connect...

If you chose to start the debugger manually or the debugger does not appear due to an error, start a supported debugger now and enter the following command at the debugger prompt:  target remote :44749

# Option â-xâ-- â

2. I start gdb in a new terminal window, connect to the target, set breakpoint and run program execution. But unfortunately, a warning message is printed and debugger doesn't stop on specified breakpoint :

sh-4.4# gdb /localdisk2/github/build/debug/bin/sycl-post-link
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /localdisk2/github/build/debug/bin/sycl-post-link...done.
(gdb) target remote :45317
Remote debugging using :45317
warning: remote target does not support file transfer, attempting to access files from local filesystem.
Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/ld-2.27.so...done.
done.
0x00007fc547617090 in _start () from /lib64/ld-linux-x86-64.so.2
(gdb) b sycl-post-link.cpp:824
Breakpoint 1 at 0xb7bf8: file /localdisk2/github/llvm/llvm/tools/sycl-post-link/sycl-post-link.cpp, line 824.
(gdb) c
Continuing.
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.

[Inferior 1 (Remote target) exited normally]

What should I do to fix this problem?

[ArunJ_Intel]

Hi Mikhail_L

Could you share the command line that you have used to run the inspector session. (In case if you are trying to run mi1 analysis the debugger is not supported for the mi1 analysis type.)

Could you also try out running/debugging the executable independently with gdb, ie without using intel inspector. Let us know if you are able to run the executable normally and set breakpoints in the same line when not using inspector.

edit:1

From the name of the executable we assume the application you are using is sycl/dpc++. Could you let us know if this is a dpc++ application. Also try running inspector and gdb with a basic c++ application and see if setting the breakpoints works. We would suggest using any one of the samples that are available in the inspector installation directory({INSPECTOR_INSTALLED_PATH}/samples/en)

Thanks

Arun

[ArunJ_Intel]

Hi Mikhail_L,

Have you tried out the options mentioned, Please let us know your observations.

Thanks

Arun Jose

[ArunJ_Intel]

Hi Mikhail_L

We assume that your issue is resolved. If you need any further assistance, please post a new question as this thread will no longer be monitored by Intel.

Thanks

Arun