Re: breakpoints in shared libraries

Maybe the window was opened under the DDD window?

On 5/19/23 06:05, [email protected] wrote:
> I am now getting a popup asking if the breakpoint is in a shared 
> library. I don't know why I didn't get it (see it?) before I sent my 
> previous email.
> 
> Regards,
> Peter
> 
> Peter Epstein
> Siemens Digital Industries Software
> 5114 Raymond Rd.
> Madison WI 53711 USA
> Office: +1 (608) 271-1219
> Mobile: +1 (608) 571-8413
> [email protected] <mailto:[email protected]>
> www.siemens.com/plm <http://www.siemens.com/plm>
> ------------------------------------------------------------------------
> *From:* Epstein, Peter (DI SW STS SDDEV SRV DISC R&D)
> *Sent:* Friday, May 12, 2023 8:34 AM
> *To:* [email protected] <[email protected]>
> *Subject:* breakpoints in shared libraries
> 1 - Thank you for reviving ddd. I have missed it.
> 
> 2 - When I run gdb from the command line and try to set a break point 
> ("b cudaDebug") in a shared library, it responds with:
> 
> Function "cudaDebug" not defined.
> Make breakpoint pending on future shared library load? (y or [n])
> 
> When I run "b cudaDebug" in ddd at the "(gdb)" prompt, it just responds 
> with:
> 
> Function "cudaDebug" not defined.
> 
> I used the "--debugger" option of ddd to be sure I am using the same 
> version of gdb (13.1).
> 
> Is this expected? Will it be changed in the future?
> 
> Regards,
> Peter
> 
> Peter Epstein
> Siemens Digital Industries Software
> 5114 Raymond Rd.
> Madison WI 53711 USA
> Office: +1 (608) 271-1219
> Mobile: +1 (608) 571-8413
> [email protected] <mailto:[email protected]>
> www.siemens.com/plm <http://www.siemens.com/plm>

-- 
Michael Eager