Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
Qt Creator 15.0.1
-
None
-
Linux/Wayland
Description
working on the qtmultimedia/ffmpeg plugin, i've seen some odd behaviour using qtc with lldb on linux when debugging ffmpeg's libraries:
- when i set a breakpoint by function name, the breakpoint is resolved and triggered and i can step through the code
- when i set the breakpoint by file/line, the breakpoint is not resolved:
lldb gives me the following log:
d[LLDB] TAKING OWNERSHIP OF BREAKPOINT 48
<1820insertBreakpoint({"address":0,"command":"","condition":"","enabled":1,"expression":"","file":"/home/tim/dev/ffmpeg/libavcodec/aacenc.c","function":"","id":"","ignorecount":0,"line":1231,"modelid":48,"oneshot":0,"token":1820,"type":1})
>(lldb) script theDumper.insertBreakpoint({"address":0,"command":"","condition":"","enabled":1,"expression":"","file":"/home/tim/dev/ffmpeg/libavcodec/aacenc.c","function":"","id":"","ignorecount":0,"line":1231,"modelid":48,"oneshot":0,"token":1820,"type":1})
>@
>result={token="1820",lldbid="8",valid="1",hitcount="0",threadid="0",oneshot="0",condition="",enabled="1",valid="1",ignorecount="0",locations=[]}@
>1820^
d[LLDB] NO LOCATIONS (YET) FOR BP Type: 0 [enabled] [pending] Hit: 0 times
when using gdb, setting the breakpioint by line works fine:
d[GDB] TAKING OWNERSHIP OF BREAKPOINT 53 d[GDB] RUNNING NEEDS-STOP COMMAND -break-insert -f "\"aacenc.c\":1231" <320-break-insert -f "\"aacenc.c\":1231" >320^done,bkpt={number="13",type="breakpoint",disp="keep",enabled="y",addr="0x00007fffe26b290b",func="alloc_buffers",file="src/libavcodec/aacenc.c",fullname="/home/tim/dev/ffmpeg/libavcodec/aacenc.c",line="1231",thread-groups=["i1"],times="0",original-location="aacenc.c:1231"}