[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-29 Thread via lldb-commits
oltolm wrote: Can you backport it into llvm-19 branch? This bug makes lldb-dap almost impossible to use on Windows. https://github.com/llvm/llvm-project/pull/104874 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-b

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-26 Thread via lldb-commits
jimingham wrote: This is compiling the "get me extended backtrace info function". That's a ClangFunction, so we should only compile it once and then reuse it for the rest of the session. Is it possible we aren't reusing this? After all, this is a compile of a function that's pretty careful

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-23 Thread via lldb-commits
jeffreytan81 wrote: And just for fun, here is an extreme one with 18 seconds of sampling time, 99.6% time is from this hot path. Note: they are all from linux machines because we only enable perf sampling by default for linux platform so we have no Mac data. ``` # time of first sample : 26469

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-23 Thread via lldb-commits
jeffreytan81 wrote: As another data point, I just encountered a telemetry data from a customer. Taking profile trace from that session shows "stackTrace" request takes more than 4 seconds. Around 94% of the time was spent in this hot path performing function evaluation: ``` ll

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-22 Thread John Harrison via lldb-commits
ashgti wrote: I'll try to work that into my refactor of the call for `thread.GetCurrentExceptionBacktrace()` https://github.com/llvm/llvm-project/pull/104874 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mail

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-22 Thread Greg Clayton via lldb-commits
@@ -3111,17 +3115,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-22 Thread Greg Clayton via lldb-commits
clayborg wrote: >From the DAP protocol for "StackTraceRequest", I see this in the response: ``` /** * The total number of frames available in the stack. If omitted or if * `totalFrames` is larger than the available frames, a client is expected * to request frames until a reques

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-22 Thread Greg Clayton via lldb-commits
https://github.com/clayborg commented: You didn't add the new launch config variable to the package.json. Please add with a new PR with descriptions. https://github.com/llvm/llvm-project/pull/104874 ___ lldb-commits mailing list lldb-commits@lists.llv

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-22 Thread via lldb-commits
https://github.com/jeffreytan81 closed https://github.com/llvm/llvm-project/pull/104874 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread John Harrison via lldb-commits
@@ -3111,17 +3115,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread Walter Erquinigo via lldb-commits
https://github.com/walter-erquinigo approved this pull request. I'm approving this to unblock. https://github.com/llvm/llvm-project/pull/104874 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/l

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread via lldb-commits
@@ -3111,17 +3115,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread Walter Erquinigo via lldb-commits
@@ -3111,17 +3115,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread via lldb-commits
@@ -3111,17 +3115,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread Walter Erquinigo via lldb-commits
@@ -3111,17 +3115,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread via lldb-commits
@@ -3111,17 +3115,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread Walter Erquinigo via lldb-commits
@@ -3111,17 +3115,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread John Harrison via lldb-commits
@@ -3111,17 +3115,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread via lldb-commits
@@ -3091,17 +3093,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread via lldb-commits
https://github.com/jeffreytan81 updated https://github.com/llvm/llvm-project/pull/104874 >From 6e84ab9a14e63c58e1facdbf9a695c093882b37b Mon Sep 17 00:00:00 2001 From: jeffreytan81 Date: Mon, 19 Aug 2024 10:57:35 -0700 Subject: [PATCH 1/2] Fix StartDebuggingRequestHandler/ReplModeRequestHandler

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread via lldb-commits
jeffreytan81 wrote: @walter-erquinigo, the performance issue is not only showing for 1% rare gigantic target. It is actually reported by a customer's target with 4000 modules with only 3GB of debug info. Disabling this feature significantly improves the stepping experience. To get a sense of

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread Walter Erquinigo via lldb-commits
@@ -3091,17 +3093,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread Greg Clayton via lldb-commits
@@ -3091,17 +3093,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread Greg Clayton via lldb-commits
@@ -3091,17 +3093,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-21 Thread John Harrison via lldb-commits
@@ -3091,17 +3093,20 @@ void request_stackTrace(const llvm::json::Object &request) { // This will always return an invalid thread when // libBacktraceRecording.dylib is not loaded or if there is no extended // backtrace. -lldb::SBThread queue_backtrace_thread =

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-20 Thread Walter Erquinigo via lldb-commits
@@ -701,6 +701,8 @@ void request_attach(const llvm::json::Object &request) { GetBoolean(arguments, "enableAutoVariableSummaries", false); g_dap.enable_synthetic_child_debugging = GetBoolean(arguments, "enableSyntheticChildDebugging", false); + g_dap.enable_displa

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-20 Thread Walter Erquinigo via lldb-commits
https://github.com/walter-erquinigo requested changes to this pull request. @jeffreytan81 , could you make the default to be true if the current platform is Mac? The extension should just work nicely for the 99% of people who don't use massive binaries. https://github.com/llvm/llvm-project/pul

[Lldb-commits] [lldb] Fix dap stacktrace perf issue (PR #104874)

2024-08-20 Thread Walter Erquinigo via lldb-commits
walter-erquinigo wrote: @ashgti , do you have any opinions on this? https://github.com/llvm/llvm-project/pull/104874 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits