Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
SlickEdit® / Re: Execute menu option is greyed out
« Last post by Clark on February 09, 2025, 03:53:37 PM »
If this normally has those menu items enabled, sometimes there's a delay in the menu updating. Restart SlickEdit if the menu remains incorrect.

Note that your'e not on the latest version of v28. The latest version is 28.0.2. Although, I don't expect updating to change what you are seeing here.
72
SlickEdit® / Execute menu option is greyed out
« Last post by gkl on February 09, 2025, 03:43:23 PM »
Dear All,

I am on 28.0.1 on Windows 11 and out of the blue, the Execute option under Build is greyed out. I would usually have single Python files that I will execute by going to the Build menu and selecting Execute. Now, this option is greyed out as seen in the attached image. How can I bring it back?

Best Regards,
George
73
SlickEdit® / Re: Unable to debug on macOS
« Last post by Clark on February 07, 2025, 08:02:54 PM »
glad this works for you.

v30 there will have support for CMake's new file API. It's really good. Much better and more convenient that the old cmake support. Although you will have to manually change the compiler options if you want to be able to debug on macOS. No way to automate that.
74
SlickEdit® / Re: Unable to debug on macOS
« Last post by PaulElliott on February 07, 2025, 04:26:57 PM »
This was with the clang workspace, my other projects are too complex for simple tests / built externally.

This was extremely curious. It didn't work until I started messing around with dsymutil on clang_prog, trying to ascertain what debug version it was using. At some point during this, breakpoints started catching again. I have since tried to break this by removing the files that this produces, but to no avail. For now, I will just take the win I think.

I will report back if I can find anything more on this, given many of my projects are being built externally with cmake, this is still something of an issue which won't get resolved with the hotfix either.
75
SlickEdit® / Re: Unable to debug on macOS
« Last post by Clark on February 07, 2025, 01:48:26 AM »
Have you tried debugging with the clang sample?

Project>All Workspaces>Sample Workspaces>clang.vpw
76
SlickEdit® / Re: Unable to debug on macOS
« Last post by PaulElliott on February 07, 2025, 12:01:53 AM »
Yep, definitely building debug, like I say, I can see the option on the build command line.

Only major difference then is I am running 15.2, but its still Apple clang version 16.0.0 (clang-1600.0.26.6) - I'm not entirely sure there was an upgrade.

Looks like I need to do some elf Mach-O analysis in the morning. Any hints and tips on this would be greatly appreciated, I know my way around an elf file, but but new on Mach-O.
77
SlickEdit® / Re: Unable to debug on macOS
« Last post by Clark on February 06, 2025, 11:25:01 PM »
Upgrading to v29 shouldn't be required. The only change in v29 is automation for adding the extra compile option.

Make sure you build the Debug config and not Release. Build>Set Active Configuration

Debug won't work in a Release config

78
SlickEdit® / Re: Unable to debug on macOS
« Last post by PaulElliott on February 06, 2025, 12:43:10 PM »
Quote from: Clark on February 05, 2025, 05:58:28 PM
Make sure you clear out the following setting:
Tools>Options>Debugging>General>Debug Server executable
Restart SlickEdit before trying to debug.

Hi Clark, definitely done that, I wasn't even able to start debugging until that was done, and that definitely fixes that, many thanks with your help catching that.

Now when I start debugging, the executable just runs straight through and no breakpoints catch. I have followed the instructions above on the clang project, checked that -fdebug-default-version=4 is definitely included on the build command line, however no breakpoints set in the editor are caught, the same symptoms as described in the initial post.

The only major difference here is that I am running v28 (hence no hot fix, so using the manual instructions). My question therefore, is whether or not this fix is expected to work in v28 with apple clang 16, or whether upgrading to v29 is required here.
79
SlickEdit® / Re: Unable to debug on macOS
« Last post by Clark on February 05, 2025, 05:58:28 PM »
Quote from: PaulElliott on February 05, 2025, 05:30:14 PM
Hi all,
The above manual instructions do not seem to work for me (debug breakpoints still don't catch) on v28. Is this to be expected, and we have to upgrade to v29 to fix?
Make sure you clear out the following setting:

Tools>Options>Debugging>General>Debug Server executable

Restart SlickEdit before trying to debug.
80
SlickEdit® / Re: Unable to debug on macOS
« Last post by PaulElliott on February 05, 2025, 05:30:14 PM »
Hi all,
The above manual instructions do not seem to work for me (debug breakpoints still don't catch) on v28. Is this to be expected, and we have to upgrade to v29 to fix?
Pages: 1 ... 6 7 [8] 9 10