Walter Erquinigo
MModular
•Created by obadakhalili on 4/8/2024 in #questions
Debugging Issue with Mojo's VSCode Debugger
I'll be OOO for one week. I can come back to help you after that 😦
38 replies
MModular
•Created by xentropy on 8/27/2024 in #questions
mojo-lsp-server crashing
Awesome! Now it's just about the issue that xentry po is running into
35 replies
MModular
•Created by obadakhalili on 4/8/2024 in #questions
Debugging Issue with Mojo's VSCode Debugger
About this, I'm making a change that will appear in the nightly version that will make this easier:
38 replies
MModular
•Created by obadakhalili on 4/8/2024 in #questions
Debugging Issue with Mojo's VSCode Debugger
If you want a solution that works in both VSCode and the terminal, you can create an
.lldbinit
file in your home directory (e.g. $USER/.lldbinit
), and add this single line there
That should prevent LLDB from using the personality
syscall that disables address space layout randomization, which ends up using the personality syscall.
If that works, I'll probably add a --disable-aslr
flag to mojo debug
for convenience.
The JSON debug config in VS Code already has a flag for this (disableASLR
), although I really don't like writing .json configs.38 replies
MModular
•Created by obadakhalili on 4/8/2024 in #questions
Debugging Issue with Mojo's VSCode Debugger
If you have personality set failed, we can get await with a trick.
38 replies
MModular
•Created by xentropy on 8/27/2024 in #questions
mojo-lsp-server crashing
@Lily Brown should be able to help with this next week because I'll be on vacations
35 replies
MModular
•Created by xentropy on 8/27/2024 in #questions
mojo-lsp-server crashing
Plesae, send the entire log
35 replies
MModular
•Created by xentropy on 8/27/2024 in #questions
mojo-lsp-server crashing
I'm almost sure that the
scaling_cur_freq
error message is benign. It's used to compute some performance bits when available for telemetry.
What I think is the actual error is the following:
I'll have someone on the team debug this35 replies
MModular
•Created by obadakhalili on 4/8/2024 in #questions
Debugging Issue with Mojo's VSCode Debugger
I see. That means that you are using the stable mojo extension. If you are using the nightly SDK, then you should juse the nightly extension from https://marketplace.visualstudio.com/items?itemName=modular-mojotools.vscode-mojo-nightly
Every fix that we may do in the extension will be reflected in the nightly version.
The stable version is updated probably every 3 months
38 replies
MModular
•Created by obadakhalili on 4/8/2024 in #questions
Debugging Issue with Mojo's VSCode Debugger
38 replies
MModular
•Created by obadakhalili on 4/8/2024 in #questions
Debugging Issue with Mojo's VSCode Debugger
In any case, tomorrow I'll work on a few changes that will make this easier to do
38 replies
MModular
•Created by xentropy on 8/27/2024 in #questions
mojo-lsp-server crashing
Has this gotten better with the last nightly?
35 replies
MModular
•Created by obadakhalili on 4/8/2024 in #questions
Debugging Issue with Mojo's VSCode Debugger
@Hylke FYI
38 replies
MModular
•Created by obadakhalili on 4/8/2024 in #questions
Debugging Issue with Mojo's VSCode Debugger
Hi, I'm the debugger guy at modular and sorry for chiming it late.
Have you tried doing the following in the nightly version:
You can also do
and that will launch the session on vscode
38 replies
MModular
•Created by xentropy on 8/27/2024 in #questions
mojo-lsp-server crashing
Could one share some code snippet that makes the LSP crash?
35 replies
MModular
•Created by wigging on 3/1/2024 in #questions
Set breakpoint in Mojo code
We have already worked on this feature! It'll be available in the release
2 replies