Recent Posts

Pages: 1 2 [3] 4 5 ... 10
SlickEdit® / Re: SlickEdit on MacOS
« Last post by Clark on December 08, 2017, 03:53:45 pm »
You can configure the gdb that SlickEdit uses when debugging GDB projects.

SlickEdit doesn't provide anything for code signing.

Most people use clang on macOS but if you need to use GDB, it really won't make much difference. As for hooks into LLVM hooks, you can change the compiler used but you can't really replace the debugger (it would be a hack by replacing a shared library included with SlickEdit).

When you create a Clang or GNU project in SlickEdit, the wizard will ask you how you want to do your builds. One of the options is to use your on manually maintained makefile that you provide. The default option is not to use a makefile at all and use SlickEdit's build system. Another option is provided where SlickEdit generates the makefile and updates it for you (don't choose that for a pre-existing makefile).
SlickEdit® / Re: SlickEdit on MacOS
« Last post by GaryFerland on December 08, 2017, 01:25:37 pm »
Turns out there is a gdb available from homebrew - but getting it to work requires signing system security certificates, as described in the following:
Can SlickEdit only use the gdb that comes with it or can it use the homebrew version?  The SlickEdit gdb would likely need this same certificate signing process.

What compiler do most people use when developing with SlickEdit on MacOS?  The Apple command line tools LLVM?  Does SlickEdit have hooks into that version of the LLVM debugger?

What about the makefiles?
SlickEdit® / Re: Regex Evaluator seems Lost!
« Last post by dfechser on December 08, 2017, 01:02:33 am »
I'm still seeing this problem the first time I open the Regex Evaluator after restarting my PC.
Is there any way to tell SlickEdit not to do this?
SlickEdit® / Re: SlickEdit on MacOS
« Last post by Clark on December 07, 2017, 10:01:02 pm »
I don't think there is a great workaround for the diff settings issue. It shouldn't take us long to fix this. We will update this post when we have something.

If homebrew gcc-6 generates objects that are compatible with gdb, then you should be able to get full debugging support for it using SlickEdit. SlickEdit ships with a gdb for macOS (macos/gdb). Try using it as a command line debugger. If that works, you should be able to use SlickEdits GUI debugger with it. As long as homebrew gcc-6 command line works similar to standard gcc, then you can also take advantage of all of SlickEdit's build support. After creating a GNU C/C++ project in SlickEdit, configure the compiler here (Project>Project Properties, choose the Tools tab, select the "Build" tool, Click "Options...", set the Compiler field in the Compiler tab).
SlickEdit® / Re: v22 memory leak?
« Last post by IkerAriz on December 07, 2017, 09:48:12 pm »
Great to hear! Thanks for the follow up.


SlickEdit® / Re: List current context is showing the wrong context in python file
« Last post by rowbearto on December 07, 2017, 09:44:01 pm »

I just loaded hotfix 11 and the 2nd issue is still there.

Also also click the +/- on startSim, but I see a different result than you (see attached).

SlickEdit® / Re: SlickEdit on MacOS
« Last post by GaryFerland on December 07, 2017, 09:27:37 pm »
is there an ini file that I could edit to adjust it manually?

A couple of newbie questions - maybe you could point me to the right documentation.
The SlickEdit website says it offers debugging with both GCC and LLVM.  The Macs have apple command line tools LLVM and homebrew gcc-6.  LLVM does have a command line debugger but homebrew does not offer gdb.  How does Slickedit do debugging in this case?  Does it have its own Mac version of gdb with hooks into it from the IDE?  Does Slickedit provide a ddd-like graphical top end to both debuggers?

We are set up with gnu makefiles (not cmake).  Can SlickEdit ingest a standard makefile to control the build?

SlickEdit® / Re: List current context is showing the wrong context in python file
« Last post by Lee on December 07, 2017, 09:22:23 pm »
Thanks for the report and the sample.  The second bug report I can confirm is already fixed in in Hotfix revision 11, there was a bug with List all and <Current Procedure> not working correctly.

The first one is a limitation in context handler for the search results. For line 290, the tagging engine reports the current context as a member variable instantiation for self.ShelfNum, which is correct.  Currently for search results, it only cares if the current context is function/procedure type and and isn't searching for outer contexts.  There are plans to expand current context feature for search results in a later release, but it is going to need a lot more work.  It is very limited at this time. 

Also, there needs to be a visual separator for when a specific function context ends, and the next item is in an unlisted context type (or global context).  In the first example, if you double-click to collapse the -/+ on the NELayout::Slot::startSim() function, you can see that only line 203 is grouped under that context.   There isn't a separator following it for the results on 290, and it looks like they are grouped when they shouldn't be.  That one I should be able to hotfix.
SlickEdit® / Re: Nested struct type...
« Last post by Dennis on December 07, 2017, 08:48:29 pm »
This will be fixed in the upcoming 22.0.1 maintenance release.

The Preview window tends to go for broke if it can't find a symbol's definition using conventional context tagging, it will just display any symbol with a matching name if all else fails.  It's better than nothing and can be helpful, but knowing that, you have to take what it shows with a grain of salt.  It corresponds with the results you might get if you do a Ctrl+Dot on the same symbol, the tagging engine will try to resolve the symbol using Context Tagging, but if the intelligent stuff fails, it falls back to just finding something with a name that matches.
SlickEdit® / Re: Nested struct type...
« Last post by joecar on December 07, 2017, 08:22:44 pm »
I did notice that Preview shows the wrong definition of the sub-member .value...

i.e. Preview shows struct name .value in each of these instances:

   if (gfo->priority.supported.value[0])
             return gfo->priority.range[index].value[1] & 0x7f;

Pages: 1 2 [3] 4 5 ... 10