Re: How parse a file while disable backgroound parsing in Setting?
Ivan Kush <[email protected]>
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <[email protected]> |
Sorry, take my words back. Seems, in Windows it also parses opened file, while Background parsing is disabled > Hmm, but in Linux (KDevelop 5.0.1 from AntegrOS repositories) it's a bit a viable option: I disabled Background parsing. But when open a file KDevelop parses file (of course may not find files with methods' definitions, but parses data types, current file's functions and headers-files of used classes' ). But in Windows KDevelop doesn't do it with opened files =( -- Best wishes, Ivan Kush 21.10.2016, 13:17, "Ivan Kush" <[email protected]>: > files from crash report window (see attached window). Is it sufficient or needed a dump from VS/ProcDump? > https://yadi.sk/d/6OOZim5LxJPXS > > I click "Cancel" (отмена in Russian) instead of "Send Data" and KDevelop closes. > > > Well, let's fix the crash then. Disabling the background parser is not > > really a viable option when you want to use KDevelop. > > Hmm, but in Linux (KDevelop 5.0.1 from AntegrOS repositories) it's a bit a viable option: I disabled Background parsing. But when open a file KDevelop parses file (of course may not find files with methods' definitions, but parses data types, current file's functions and headers-files of used classes' ). But in Windows KDevelop doesn't do it with opened files =( > > -- > Best wishes, > Ivan Kush > > 20.10.2016, 19:32, "Kevin Funk" <[email protected]>: >> On Thursday, 20 October 2016 18:22:52 CEST Sven Brauch wrote: >>> On 20/10/16 14:12, Ivan Kush wrote: >>> > With background parsing KDEvelop is crashed, so I disabled it. >>> > But now I can't jump to func definitions. etc. or see any tooltips >>> >>> Well, let's fix the crash then. Disabling the background parser is not >>> really a viable option when you want to use KDevelop. >> >> Yep. >> >> @Ivan: Please run KDevelop through a debugger and try to get us a core dump. >> >> ProcDump seems useful for that in case you don't have a Visual Studio around >> (never tried myself): >> https://blogs.msdn.microsoft.com/debugger/2009/12/30/what-is-a-dump-and-how-do-i-create-one/ >> >> Please upload the dump $somewhere. >> >> Cheers, >> Kevin >> >>> Greetings, >>> Sven >> >> -- >> Kevin Funk | [email protected] | http://kfunk.org