Open borjamunozf opened 1 week ago
Probaby related to #63973
I guess there is no solution, we have to keep suffering cppdbg with gdb.
@llvm/issue-subscribers-lldb
Author: None (borjamunozf)
Seems to be a general lldb issue, not specific to lldb-dap
It would be useful here to separate possible problems with core files from problems with symbols. To that end, can you run a process under lldb with the same executable and symbol files, and see if you see source information in places where with core files you weren't. The speculation from the other report you linked to was that this was lack of support for some gcc DWARF constructs. If that's what is going on, just loading the executable & symbol file into lldb and running source info -f some_source_file.c
should also fail.
The title threw me off a bit because "why would you want to set breakpoints in a core file"... And certainly you can't "hit" them since core files can't execute (at least on any system I know about).
You're right about setting the breakpoints in the core dump, my fault. I mxied with other stuf I'm working on! With the title I was referring for not reaching breakpoint it was more to the core dump line or source code.
It would be useful here to separate possible problems with core files from problems with symbols. To that end, can you run a process under lldb with the same executable and symbol files, and see if you see source information in places where with core files you weren't. The speculation from the other report you linked to was that this was lack of support for some gcc DWARF constructs. If that's what is going on, just loading the executable & symbol file into lldb and running
source info -f some_source_file.c
should also fail.
So my issue, as whole, its:
Edited:
lldb
> settings set target.source-map /asdshell /mypath/whatever
> settings set target.exec-search-paths /mnt/disk1/asd/lib:blablablalba/sysroots
> target create --core /mypath/whatever/coreDump /mnt/disk1/app/bin/WhateverApp
> bt all
gdb-multiarch /mnt/disk1/app/bin/WhateverApp coreDump
> bt
Hello! Trying to debug a core dump that works with GDB and Vscode but it does not with lldb-dap / lldb.
Working config with vscode - gdb
Trying to mimick functionality with lldb-dap:
The warning message with loading target symbols from .debug:
Info from breakpoints:
If I try to put the breakpoint other file it shows:
Show source map:
I'll be happy to provide any info! Thanks a lot.