From adrenalinedj at gmail.com Mon May 1 10:21:08 2017 From: adrenalinedj at gmail.com (JeremY Larrieu) Date: Mon, 1 May 2017 10:21:08 +0200 Subject: [Qt-creator] Plugin development - Anubis language support Message-ID: Hello, With Tobias advices, i take a look to the Nim language plugin to help me developing my plugin. Now, the plugin can detect automatically toolchains and kits (as in Android plugin). But when I run Qtcreator, i saw that my compiler is not selected in the dropdown. How can i make it selected ? How to associate a kit and a toolchain ? Thanks in advance. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture du 2017-05-01 10-19-47.png Type: image/png Size: 163762 bytes Desc: not available URL: From Tobias.Hunger at qt.io Wed May 3 15:14:34 2017 From: Tobias.Hunger at qt.io (Tobias Hunger) Date: Wed, 3 May 2017 13:14:34 +0000 Subject: [Qt-creator] Plugin development - Anubis language support In-Reply-To: References: Message-ID: Hi JeremY, Based on your screenshot: My guess is that Qt Creator does not have any compiler defined for your language. What does the Tool chains tab show? Is there an anubis compiler listed there? Best Regards, Tobias From adrenalinedj at gmail.com Wed May 3 18:37:07 2017 From: adrenalinedj at gmail.com (JeremY Larrieu) Date: Wed, 3 May 2017 18:37:07 +0200 Subject: [Qt-creator] Plugin development - Anubis language support In-Reply-To: References: Message-ID: Hello, As you can see in the new screenshot attached, the Anubis compiler is auto detected. Here is the code to "auto-detect" kits based on the "auto detected Anubis toolchains" (it's based on what i found in the android plugin): const QList existingKits = Utils::filtered(ProjectExplorer::KitManager::kits(), [](const ProjectExplorer::Kit *k) { return k->isAutoDetected(); }); QList newKits; const QList filteredToolchains = ProjectExplorer::ToolChainManager::toolChains([](const ProjectExplorer::ToolChain *tc) { return tc->isAutoDetected() && tc->isValid() && tc->typeId() == Constants::AnubisToolchainId; }); const QList toolchains = Utils::transform(filteredToolchains, [](ProjectExplorer::ToolChain *tc) { return static_cast(tc); }); for (AnubisToolChain *tc : toolchains) { ProjectExplorer::Kit *newKit = new ProjectExplorer::Kit; newKit->setAutoDetected(true); newKit->setAutoDetectionSource("PyramIDEConfiguration"); auto findExistingKit = [newKit](const ProjectExplorer::Kit *k) { return matchKits(newKit, k); }; ProjectExplorer::Kit *existingKit = Utils::findOrDefault(existingKits, findExistingKit); if (existingKit) { ProjectExplorer::KitManager::deleteKit(newKit); newKit = existingKit; } auto keys = newKit->allKeys(); for (Core::Id key : keys) { qDebug("key => " + key.toString().toLatin1() + " | value => " + newKit->value(key).toString().toLatin1()); } auto toto = newKit->toHtml(); qDebug("html:\n" + toto.toLatin1() + "\n"); newKit->makeSticky(); newKit->setUnexpandedDisplayName(QObject::tr("Anubis %1").arg(tc->compilerVersion())); if (!existingKit) { ProjectExplorer::KitManager::registerKit(newKit); } } It's triggered in the plugin entry point (initialize method) on the "kitsLoaded" signal of KitManager: connect(KitManager::instance(), &KitManager::kitsLoaded, this, &PyramIDEPlugin::kitsRestored); void PyramIDEPlugin::kitsRestored() { PyramIDEConfigurations::updateAutomaticKitList(); disconnect(KitManager::instance(), &KitManager::kitsChanged, this, &PyramIDEPlugin::kitsRestored); } Thanks for your help. Jeremy 2017-05-03 15:14 GMT+02:00 Tobias Hunger : > Hi JeremY, > > Based on your screenshot: My guess is that Qt Creator does not have any > compiler defined for your language. > > What does the Tool chains tab show? Is there an anubis compiler listed > there? > > Best Regards, > Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture du 2017-05-03 18-23-17.png Type: image/png Size: 123095 bytes Desc: not available URL: From igor.mironchik at gmail.com Thu May 4 10:31:32 2017 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Thu, 4 May 2017 11:31:32 +0300 Subject: [Qt-creator] Bug Message-ID: Hello, I cough a bug in 4.2.2 built with Qt 5.8.0 (MSVC 2015, 32 bit) - official binaries. Let's say you have following code: #define SL const char * t[ 13 * 3 ] = { SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", SL"----", SL"122", SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", SL"----", SL"122", SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", SL"----", SL"122" }; And you want to replace SL" with SL( ". But you want to replace it in whole project. Than you are doing: Ctrl+F -> Advanced -> Search for SL" -> Search & Replace -> Replace with: SL( " -> Replace. And you will get something similar to: #define SL const char * t[ 13 * 3 ] = { SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122", SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122", SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122" }; Not all SL" were changed... Is it a known bug? Thank you. --- This email has been checked for viruses by AVG. http://www.avg.com From Eike.Ziller at qt.io Thu May 4 10:43:51 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Thu, 4 May 2017 08:43:51 +0000 Subject: [Qt-creator] Bug In-Reply-To: References: Message-ID: > On May 4, 2017, at 10:31 AM, Igor Mironchik wrote: > > Hello, > > I cough a bug in 4.2.2 built with Qt 5.8.0 (MSVC 2015, 32 bit) - official binaries. > > Let's say you have following code: > > > #define SL > > const char * t[ 13 * 3 ] = { > SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", > SL"-as", SL"-jh", SL"-hj", SL"----", SL"122", SL"a", SL"abc", SL"-a", > SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", > SL"----", SL"122", SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", > SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", SL"----", SL"122" > }; > > And you want to replace SL" with SL( ". But you want to replace it in whole project. Than you are doing: > > Ctrl+F -> Advanced -> Search for SL" -> Search & Replace -> Replace with: SL( " -> Replace. > > And you will get something similar to: > > > #define SL > > const char * t[ 13 * 3 ] = { > SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", > SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122", SL"a", SL"abc", SL( "-a", > SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", > SL( "----", SL"122", SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", > SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122" > }; > > > Not all SL" were changed... > > Is it a known bug? Thank you. It seems to work here (Qt Creator 4.2.2, macOS, though I wouldn’t know why it should make a difference..). In the search result overview, before you press “replace”, are all occurrences found, and selected? If the issue persists, please create a minimal example and a bugreport on https://bugreports.qt.io . Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From Eike.Ziller at qt.io Thu May 4 10:45:10 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Thu, 4 May 2017 08:45:10 +0000 Subject: [Qt-creator] RubyCreator upstream or not upstream In-Reply-To: References: <1491608686.960.0@smtp.gmail.com> Message-ID: <66F1CC66-4C39-4B2D-B769-C8269FB88408@qt.io> > On Apr 8, 2017, at 10:12 AM, Tobias Hunger wrote: > > Hi Hugo, > > I would personally like to see a ruby plugin: I like ruby and > occasionally have to do small changes to ruby projects. Eike is the > one to make that call though. Actually I’d say the call to make is one of the maintainers taking it under their responsibilities. > This is not a decision of "in or out": We could also set up a > repository on our infrastructure and add that into the public Qt > Creator super repository (see here: > https://codereview.qt-project.org/gitweb?p=qt-creator/qtc-super.git;a=summary > ). > > Your plugin gets a bit more visibility that way and will be part of > the build of more developers. That already helps with the "we break > stuff all the time and do not even notice" problem:-) Yes, we recently set this up, with the goal of creating a lower-barrier entry point. When more things are in qtc-super, and more people are using it, this should help to better keep up with API changes. > Ideally we would even build the plugins (provided they do build at the > time) to avoid the hassle of creating plugins that are compatible with > our Qt Creator binaries. We have plans for that, but as far as I > understand the problem we will need to get Qt Creator into the Qt CI > first. So this is not happening anytime soon. Actually this is only partially true. We could do that with some work without having Qt Creator in CI. But there currently _is_ work ongoing to get Qt Creator into CI, so we can better share resources, and this will happen soon(ish(tm)). When we have solved the issues of getting the Qt Creator build into CI, this will probably also clear the way for additional plugins there. Br, Eike > Best Regards, > Tobias > > On Sat, Apr 8, 2017 at 1:44 AM, Hugo Parente Lima wrote: >> Hi QtC devs. >> >> I'm a C++ developer that 3 years ago started a job with Ruby/Web, so to not >> loss my C++ skills and to continue to use the IDE I love I started >> RubyCreator, a plugin to QtC that add support to Ruby on QtC. >> >> I use it on my daily work since then and add features when I have time and >> motivation to do so, Orgad Shaneh help me with patches adapting my plugin to >> the frequent QtC API changes (since I usually only catch these changes when >> ArchLinux updates QtC), so he also gave me the suggestion to try to push my >> plugin upstream, this would: >> >> - Reduce the headaches of adapt my code to the frequent QtC API changes. >> - Solve the problem of windows/mac compilation/distribution. >> - Have more users :-), some friends of mine use mac and refuse to waste time >> compiling things. >> >> Ok, so I ask you guys if the QtC devs have some interest in accept this >> plugin upstream, if so, some things need to be adjusted beforehand. >> >> - Convert file naming code style to QtC one. >> - Convert general code style to QtC one (I think it's already done). >> - Review all the code before let it merged (of course), since I probably >> missused some QtC API. >> >> If there is not interest, I'm fine too, and I'll just keep the development >> as it is now. >> >> Here is more info about the plugin: >> >> Outdated webpage: http://hugopl.github.io/RubyCreator/ >> Github project: https://github.com/hugopl/RubyCreator >> >> Thanks >> -- >> Hugo >> >> _______________________________________________ >> Qt-creator mailing list >> Qt-creator at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/qt-creator > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From igor.mironchik at gmail.com Thu May 4 10:46:09 2017 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Thu, 4 May 2017 11:46:09 +0300 Subject: [Qt-creator] Bug In-Reply-To: References: Message-ID: <0cb5242e-576a-75b0-566c-aaad86ae10a8@gmail.com> 2017-05-04 11:43, Eike Ziller пишет: >> On May 4, 2017, at 10:31 AM, Igor Mironchik wrote: >> >> Hello, >> >> I cough a bug in 4.2.2 built with Qt 5.8.0 (MSVC 2015, 32 bit) - official binaries. >> >> Let's say you have following code: >> >> >> #define SL >> >> const char * t[ 13 * 3 ] = { >> SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", >> SL"-as", SL"-jh", SL"-hj", SL"----", SL"122", SL"a", SL"abc", SL"-a", >> SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", >> SL"----", SL"122", SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", >> SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", SL"----", SL"122" >> }; >> >> And you want to replace SL" with SL( ". But you want to replace it in whole project. Than you are doing: >> >> Ctrl+F -> Advanced -> Search for SL" -> Search & Replace -> Replace with: SL( " -> Replace. >> >> And you will get something similar to: >> >> >> #define SL >> >> const char * t[ 13 * 3 ] = { >> SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", >> SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122", SL"a", SL"abc", SL( "-a", >> SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", >> SL( "----", SL"122", SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", >> SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122" >> }; >> >> >> Not all SL" were changed... >> >> Is it a known bug? Thank you. > It seems to work here (Qt Creator 4.2.2, macOS, though I wouldn’t know why it should make a difference..). > In the search result overview, before you press “replace”, are all occurrences found, and selected? > If the issue persists, please create a minimal example and a bugreport on https://bugreports.qt.io . Did you try to replace in whole project using Advanced search and replace? Usual Replace in one file works, doesn't work replace with Advanced options... --- This email has been checked for viruses by AVG. http://www.avg.com From Eike.Ziller at qt.io Thu May 4 10:47:18 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Thu, 4 May 2017 08:47:18 +0000 Subject: [Qt-creator] Bug In-Reply-To: <0cb5242e-576a-75b0-566c-aaad86ae10a8@gmail.com> References: <0cb5242e-576a-75b0-566c-aaad86ae10a8@gmail.com> Message-ID: <09122B44-5931-458E-A55F-675E648FC836@qt.io> > On May 4, 2017, at 10:46 AM, Igor Mironchik wrote: > > > > 2017-05-04 11:43, Eike Ziller пишет: >>> On May 4, 2017, at 10:31 AM, Igor Mironchik wrote: >>> >>> Hello, >>> >>> I cough a bug in 4.2.2 built with Qt 5.8.0 (MSVC 2015, 32 bit) - official binaries. >>> >>> Let's say you have following code: >>> >>> >>> #define SL >>> >>> const char * t[ 13 * 3 ] = { >>> SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", >>> SL"-as", SL"-jh", SL"-hj", SL"----", SL"122", SL"a", SL"abc", SL"-a", >>> SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", >>> SL"----", SL"122", SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", >>> SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", SL"----", SL"122" >>> }; >>> >>> And you want to replace SL" with SL( ". But you want to replace it in whole project. Than you are doing: >>> >>> Ctrl+F -> Advanced -> Search for SL" -> Search & Replace -> Replace with: SL( " -> Replace. >>> >>> And you will get something similar to: >>> >>> >>> #define SL >>> >>> const char * t[ 13 * 3 ] = { >>> SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", >>> SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122", SL"a", SL"abc", SL( "-a", >>> SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", >>> SL( "----", SL"122", SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", >>> SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122" >>> }; >>> >>> >>> Not all SL" were changed... >>> >>> Is it a known bug? Thank you. >> It seems to work here (Qt Creator 4.2.2, macOS, though I wouldn’t know why it should make a difference..). >> In the search result overview, before you press “replace”, are all occurrences found, and selected? >> If the issue persists, please create a minimal example and a bugreport on https://bugreports.qt.io . > > Did you try to replace in whole project using Advanced search and replace? Usual Replace in one file works, doesn't work replace with Advanced options... Yes, that’s what I did. -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From igor.mironchik at gmail.com Thu May 4 11:03:01 2017 From: igor.mironchik at gmail.com (Igor Mironchik) Date: Thu, 4 May 2017 12:03:01 +0300 Subject: [Qt-creator] Bug In-Reply-To: <09122B44-5931-458E-A55F-675E648FC836@qt.io> References: <0cb5242e-576a-75b0-566c-aaad86ae10a8@gmail.com> <09122B44-5931-458E-A55F-675E648FC836@qt.io> Message-ID: https://bugreports.qt.io/browse/QTCREATORBUG-18146 2017-05-04 11:47, Eike Ziller пишет: >> On May 4, 2017, at 10:46 AM, Igor Mironchik wrote: >> >> >> >> 2017-05-04 11:43, Eike Ziller пишет: >>>> On May 4, 2017, at 10:31 AM, Igor Mironchik wrote: >>>> >>>> Hello, >>>> >>>> I cough a bug in 4.2.2 built with Qt 5.8.0 (MSVC 2015, 32 bit) - official binaries. >>>> >>>> Let's say you have following code: >>>> >>>> >>>> #define SL >>>> >>>> const char * t[ 13 * 3 ] = { >>>> SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", >>>> SL"-as", SL"-jh", SL"-hj", SL"----", SL"122", SL"a", SL"abc", SL"-a", >>>> SL"--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", >>>> SL"----", SL"122", SL"a", SL"abc", SL"-a", SL"--abc", SL"123", SL"sdf", >>>> SL"sdf", SL"l", SL"-as", SL"-jh", SL"-hj", SL"----", SL"122" >>>> }; >>>> >>>> And you want to replace SL" with SL( ". But you want to replace it in whole project. Than you are doing: >>>> >>>> Ctrl+F -> Advanced -> Search for SL" -> Search & Replace -> Replace with: SL( " -> Replace. >>>> >>>> And you will get something similar to: >>>> >>>> >>>> #define SL >>>> >>>> const char * t[ 13 * 3 ] = { >>>> SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", >>>> SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122", SL"a", SL"abc", SL( "-a", >>>> SL( "--abc", SL"123", SL"sdf", SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", >>>> SL( "----", SL"122", SL"a", SL"abc", SL( "-a", SL( "--abc", SL"123", SL"sdf", >>>> SL"sdf", SL"l", SL( "-as", SL( "-jh", SL( "-hj", SL( "----", SL"122" >>>> }; >>>> >>>> >>>> Not all SL" were changed... >>>> >>>> Is it a known bug? Thank you. >>> It seems to work here (Qt Creator 4.2.2, macOS, though I wouldn’t know why it should make a difference..). >>> In the search result overview, before you press “replace”, are all occurrences found, and selected? >>> If the issue persists, please create a minimal example and a bugreport on https://bugreports.qt.io . >> Did you try to replace in whole project using Advanced search and replace? Usual Replace in one file works, doesn't work replace with Advanced options... > Yes, that’s what I did. > --- This email has been checked for viruses by AVG. http://www.avg.com From skobowsky at caos-gmbh.de Tue May 9 12:44:08 2017 From: skobowsky at caos-gmbh.de (Tilman Skobowsky) Date: Tue, 9 May 2017 12:44:08 +0200 Subject: [Qt-creator] disable CMake Server mode? Message-ID: <9a2c276a-fb38-af2a-cf62-0b7544c4d8ab@caos-gmbh.de> Hi, I have the same problem that is mentioned in QTCREATORBUG-17944 : cmake keeps reconfiguring and regenerating files resulting in reindexing all C++ files as well, which is very annoying since I use a rather large project. Is there a way to not use CMake Server mode in Qt 4.3rc1? Tilman Skobowsky -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eike.Ziller at qt.io Tue May 9 14:21:51 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Tue, 9 May 2017 12:21:51 +0000 Subject: [Qt-creator] disable CMake Server mode? In-Reply-To: <9a2c276a-fb38-af2a-cf62-0b7544c4d8ab@caos-gmbh.de> References: <9a2c276a-fb38-af2a-cf62-0b7544c4d8ab@caos-gmbh.de> Message-ID: > On May 9, 2017, at 12:44 PM, Tilman Skobowsky wrote: > > Hi, > > > I have the same problem that is mentioned in QTCREATORBUG-17944: cmake keeps reconfiguring and regenerating files resulting in reindexing all C++ files as well, which is very annoying since I use a rather large project. > Is there a way to not use CMake Server mode in Qt 4.3rc1? I think not using servermode currently is only possibly by using CMake < 3.7 Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From mike.jackson at bluequartz.net Wed May 10 04:24:49 2017 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Tue, 09 May 2017 22:24:49 -0400 Subject: [Qt-creator] disable CMake Server mode? In-Reply-To: <9a2c276a-fb38-af2a-cf62-0b7544c4d8ab@caos-gmbh.de> References: <9a2c276a-fb38-af2a-cf62-0b7544c4d8ab@caos-gmbh.de> Message-ID: <591279F1.10905@bluequartz.net> Turn off the "Automatically run CMake" from the configured kit. If you are editing a *.in file cmake sees that as a change and so will run on the next build. Mike Jackson > Tilman Skobowsky > May 9, 2017 at 6:44 AM > Hi, > > > I have the same problem that is mentioned in QTCREATORBUG-17944 > : cmake keeps > reconfiguring and regenerating files resulting in reindexing all C++ > files as well, which is very annoying since I use a rather large project. > Is there a way to not use CMake Server mode in Qt 4.3rc1? > > > Tilman Skobowsky > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikolai.kosjar at qt.io Fri May 12 08:22:42 2017 From: nikolai.kosjar at qt.io (Nikolai Kosjar) Date: Fri, 12 May 2017 08:22:42 +0200 Subject: [Qt-creator] comment blocks settings in qt creator In-Reply-To: References: Message-ID: On 04/24/2017 01:56 PM, Sadanand Ugare wrote: > Hi, > > In qt creator is it possible to change content of comment blocks. > > eg: > > /*! > * > * \param data > * \param options > * \return > */ > > here instead of "param" i can have "outparam". If possible then please > give me the detailed procedure to change the content. Do I understand you correctly, that you want to have the auto-generated code (after typing /** above a function) containing "\param" replaced with "\outparam" instead? Currently that is not possible. The known/generated commands are hard coded in [1]. Also, I do not see such a doxygen command at [2]. You are probably dealing with another documentation language than doxygen? You might want to create a feature request / "Suggestion" at https://bugreports.qt.io/ . Nikolai [1] src/plugins/cpptools/doxygengenerator.cpp [2] https://www.stack.nl/~dimitri/doxygen/manual/commands.html From andre.hartmann at iseg-hv.de Fri May 12 08:49:52 2017 From: andre.hartmann at iseg-hv.de (=?UTF-8?Q?Andr=c3=a9_Hartmann?=) Date: Fri, 12 May 2017 08:49:52 +0200 Subject: [Qt-creator] comment blocks settings in qt creator In-Reply-To: References: Message-ID: <77f88dc5-8216-b420-2135-2ee6aff1f051@iseg-hv.de> Hi, Am 12.05.2017 um 08:22 schrieb Nikolai Kosjar: > On 04/24/2017 01:56 PM, Sadanand Ugare wrote: >> Hi, >> >> In qt creator is it possible to change content of comment blocks. >> >> eg: >> >> /*! >> * >> * \param data >> * \param options >> * \return >> */ >> >> here instead of "param" i can have "outparam". If possible then please >> give me the detailed procedure to change the content. > > Do I understand you correctly, that you want to have the auto-generated > code (after typing /** above a function) containing "\param" > replaced with "\outparam" instead? Reading [1], it seems the syntax is \param[in], \param[out] and \param[inout]. > Currently that is not possible. The known/generated commands are hard > coded in [1]. Also, I do not see such a doxygen command at [2]. You are > probably dealing with another documentation language than doxygen? While the code model might detect "in" parameters automatically (value, const-ref or const-ptr), ref or ptr params may be inout or just out. Of course, except the code model could detect if such a param is only read or written within the function. André > You might want to create a feature request / "Suggestion" at > https://bugreports.qt.io/ . > > Nikolai > > > [1] src/plugins/cpptools/doxygengenerator.cpp > [2] https://www.stack.nl/~dimitri/doxygen/manual/commands.html > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > From nikolai.kosjar at qt.io Fri May 12 08:57:25 2017 From: nikolai.kosjar at qt.io (Nikolai Kosjar) Date: Fri, 12 May 2017 08:57:25 +0200 Subject: [Qt-creator] comment blocks settings in qt creator In-Reply-To: <77f88dc5-8216-b420-2135-2ee6aff1f051@iseg-hv.de> References: <77f88dc5-8216-b420-2135-2ee6aff1f051@iseg-hv.de> Message-ID: <52885cef-0900-0750-d731-fd6f1f747f98@qt.io> On 05/12/2017 08:49 AM, André Hartmann wrote: > Hi, > > Am 12.05.2017 um 08:22 schrieb Nikolai Kosjar: >> On 04/24/2017 01:56 PM, Sadanand Ugare wrote: >>> Hi, >>> >>> In qt creator is it possible to change content of comment blocks. >>> >>> eg: >>> >>> /*! >>> * >>> * \param data >>> * \param options >>> * \return >>> */ >>> >>> here instead of "param" i can have "outparam". If possible then please >>> give me the detailed procedure to change the content. >> >> Do I understand you correctly, that you want to have the auto-generated >> code (after typing /** above a function) containing "\param" >> replaced with "\outparam" instead? > > Reading [1], it seems the syntax is \param[in], \param[out] and > \param[inout]. Ahh, right. So it's doxygen :) You meant [2]. Nikolai From tyler at rosette-research.com Fri May 12 13:30:33 2017 From: tyler at rosette-research.com (=?utf-8?Q?tyler=40rr?=) Date: Fri, 12 May 2017 20:30:33 +0900 Subject: [Qt-creator] shortcuts unreliable on OS X Message-ID: Hi all, I’ve been using Creator for a few years now, mostly on a Mac, but since at least Qt 5.5 some keyboard shortcuts are unreliable or completely broken. For example, if I bind ctrl+backspace to delete with camelCase it never works.  Binding another key to the same function does work. Increasing font size with Command+ also tends to work for a while and then stop.  Two-stroke sequences beginning with ctrl-x fall into this category, too. Googling shows that there was a related regressing in the 5.5 series, but even the latest version of Creator has the problem. Like probably most developers I have various apps installed that grab keystrokes globally, remap keys, etc.  But Creator is the only app which shows this kind of problem.  The same keystrokes work fine elsewhere. I’m using the latest OS X now, but the problem has existed for at least 1-2 revisions back, unchanged. I’m using a Japanese keyboard and input method.  But again, other software is ok. Any suggestions?  This is driving me crazy and affecting my productivity.. :( Thanks! Tyler -------------- next part -------------- An HTML attachment was scrubbed... URL: From ukrkyi at gmail.com Sat May 13 02:35:19 2017 From: ukrkyi at gmail.com (=?UTF-8?B?0K/RgNC+0YHQu9Cw0LIg0KHQtdC80YfQtdC90LrQvg==?=) Date: Sat, 13 May 2017 00:35:19 +0000 Subject: [Qt-creator] Peripheral Register View for bare metal projects Message-ID: Hello everybody, Two years ago some people here were planning to add a register view for bare metal plugin. Is there any progress about it? Best regards, Yaroslav P. S. I've never used mailing lists before. Do I need to be subscribed to the list in order to post to it and get replies? -------------- next part -------------- An HTML attachment was scrubbed... URL: From chgans at gna.org Sat May 13 03:49:09 2017 From: chgans at gna.org (Ch'Gans) Date: Sat, 13 May 2017 13:49:09 +1200 Subject: [Qt-creator] Peripheral Register View for bare metal projects In-Reply-To: References: Message-ID: On 13 May 2017 at 12:35, Ярослав Семченко wrote: > Hello everybody, > > Two years ago some people here were planning to add a register view for bare > metal plugin. Is there any progress about it? Ar you taking processor/micro registers? > > Best regards, > Yaroslav > > P. S. I've never used mailing lists before. Do I need to be subscribed to > the list in order to post to it and get replies? You don't have to, but if you don't you might not receive answered if people hit 'reply' instead of 'reply to all'. My advice is to subscribe. This list is not high traffic. Chris > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > From ukrkyi at gmail.com Sat May 13 12:45:47 2017 From: ukrkyi at gmail.com (=?UTF-8?B?0K/RgNC+0YHQu9Cw0LIg0KHQtdC80YfQtdC90LrQvg==?=) Date: Sat, 13 May 2017 10:45:47 +0000 Subject: [Qt-creator] Peripheral Register View for bare metal projects In-Reply-To: References: Message-ID: Thank you for answer! > Ar you taking processor/micro registers? > Sorry, I was not very clear, I'm talking about peripheral registers, something like that: http://gnuarmeclipse.github.io/debug/peripheral-registers/. It is the memory region with registers mapped on it. So far I have only found this archive thread: http://lists.qt-project.org/pipermail/qt-creator/2014-September/004010.html. Yaroslav -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eike.Ziller at qt.io Mon May 15 10:43:57 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Mon, 15 May 2017 08:43:57 +0000 Subject: [Qt-creator] Nominating Vikas Pachdha for Approver status Message-ID: Hereby I nominate Vikas Pachdha for Approver status. He has been defacto maintaining iOS support in Qt Creator since a year. https://codereview.qt-project.org/#/q/owner:%22Vikas+Pachdha%22+status:merged,n,z Br, -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From Tobias.Hunger at qt.io Mon May 15 10:56:24 2017 From: Tobias.Hunger at qt.io (Tobias Hunger) Date: Mon, 15 May 2017 08:56:24 +0000 Subject: [Qt-creator] Nominating Vikas Pachdha for Approver status In-Reply-To: References: Message-ID: +1 from my side. I have been reviewing Vikas patches since he started. Best Regards, Tobias -- Tobias Hunger, Senior Software Engineer | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ________________________________________ From: Development on behalf of Eike Ziller Sent: Monday, May 15, 2017 10:43:57 AM To: Cc: qt-creator Subject: [Development] Nominating Vikas Pachdha for Approver status Hereby I nominate Vikas Pachdha for Approver status. He has been defacto maintaining iOS support in Qt Creator since a year. https://codereview.qt-project.org/#/q/owner:%22Vikas+Pachdha%22+status:merged,n,z Br, -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B _______________________________________________ Development mailing list Development at qt-project.org http://lists.qt-project.org/mailman/listinfo/development From Riitta-Leena.Miettinen at qt.io Mon May 15 11:10:57 2017 From: Riitta-Leena.Miettinen at qt.io (Riitta-Leena Miettinen) Date: Mon, 15 May 2017 09:10:57 +0000 Subject: [Qt-creator] Nominating Vikas Pachdha for Approver status In-Reply-To: References: Message-ID: +1 Leena > -----Original Message----- > From: Qt-creator [mailto:qt-creator-bounces+riitta-leena.miettinen=qt.io at qt- > project.org] On Behalf Of Tobias Hunger > Sent: Montag, 15. Mai 2017 10:56 > To: Eike Ziller ; > > Cc: qt-creator > Subject: Re: [Qt-creator] Nominating Vikas Pachdha for Approver status > > +1 from my side. I have been reviewing Vikas patches since he started. > > Best Regards, > Tobias > > -- > Tobias Hunger, Senior Software Engineer | The Qt Company > The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin > Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der > Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 > B > > > ________________________________________ > From: Development project.org> on behalf of Eike Ziller > Sent: Monday, May 15, 2017 10:43:57 AM > To: > Cc: qt-creator > Subject: [Development] Nominating Vikas Pachdha for Approver status > > Hereby I nominate Vikas Pachdha for Approver status. He has been defacto > maintaining iOS support in Qt Creator since a year. > > https://codereview.qt- > project.org/#/q/owner:%22Vikas+Pachdha%22+status:merged,n,z > > Br, > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Rudower Chaussee 13 > D-12489 Berlin > eike.ziller at qt.io > http://qt.io > Geschäftsführer: Mika Pälsi, > Juha Varelius, Mika Harjuaho > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB > 144331 B > > _______________________________________________ > Development mailing list > Development at qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator From jhihn at gmx.com Mon May 15 23:56:09 2017 From: jhihn at gmx.com (Jason H) Date: Mon, 15 May 2017 23:56:09 +0200 Subject: [Qt-creator] Who is responsible for the QML curly brace animation? Message-ID: Given onPropertyChanged: something() when I hit Enter at the bar: onPropertyChanged:{| something() What I get is a animation that takes me on a bad trip. What I am left with is: onPropertyChanged:{ something() What should happen is there shouldn't be an extra line inserted, onPropertyChanged:{ something() is how it should look. If it does anything at all, adding a curly brace would be nice, to leave me with: onPropertyChanged:{ something() } Which would be *perfect*. From sierdzio at gmail.com Wed May 17 09:49:46 2017 From: sierdzio at gmail.com (Tomasz Siekierda) Date: Wed, 17 May 2017 09:49:46 +0200 Subject: [Qt-creator] Who is responsible for the QML curly brace animation? In-Reply-To: References: Message-ID: On 15 May 2017 at 23:56, Jason H wrote: > If it does anything at all, adding a curly brace would be nice, to leave > me with: > onPropertyChanged:{ > something() > } > > Which would be *perfect*. > +1! Current behaviour is not useful. -------------- next part -------------- An HTML attachment was scrubbed... URL: From guenther.teufl at v-play.net Thu May 18 13:41:45 2017 From: guenther.teufl at v-play.net (=?UTF-8?Q?G=C3=BCnther_Teufl?=) Date: Thu, 18 May 2017 13:41:45 +0200 Subject: [Qt-creator] Project Wizard: Label with Hyperlink Message-ID: Hi! I was wondering if it is possible to use Hyperlinks in custom JSON-based Qt Creator Project Wizards. When adding a custom Field Page with a Label Widget, it's possible to use RichText, for example to make the text bold or add a link using the tag. The text within the tag is correctly marked as a link, but I didn't find a way to react to the linkActivated signal of the label to e.g. open the web-page. Is there a way to open links with JSON-based wizards, and if yes how? Thanks for your help! Best, Günther -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Hunger at qt.io Thu May 18 15:08:21 2017 From: Tobias.Hunger at qt.io (Tobias Hunger) Date: Thu, 18 May 2017 13:08:21 +0000 Subject: [Qt-creator] Project Wizard: Label with Hyperlink In-Reply-To: References: Message-ID: Hello Günther, > I was wondering if it is possible to use Hyperlinks in custom JSON-based Qt Creator Project Wizards. > When adding a custom Field Page with a Label Widget, it's possible to use RichText, for example to make the text bold or add a link using the tag. > The text within the tag is correctly marked as a link, but I didn't find a way to react to the linkActivated signal of the label to e.g. open the web-page. > Is there a way to open links with JSON-based wizards, and if yes how? Not that I am aware of:-) How would you want that handled? Is it enough to always open an external web browser? That kind of functionality should be easy to add. > Thanks for your help! You are welcome. Best Regards, Tobias -- Tobias Hunger, Senior Software Engineer | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From broothy at gmail.com Thu May 18 11:45:40 2017 From: broothy at gmail.com (=?UTF-8?B?w4Fkw6FtIEJhbMOhenM=?=) Date: Thu, 18 May 2017 11:45:40 +0200 Subject: [Qt-creator] Qt Creator predefined macro file Message-ID: Hi, Our project has a predefined macro file that is given to the compiler (GCC/Clang) with the -imacros flag. It contains the platform specific macros so it is a complicated and long file. Can I specify a predefined macro file in Qt Creator because without it the code completion fails? I know that I can specify my macros in the DEFINES section of the .pro file but we have them in a standalone file. It is not possible to move them into the .pro file because other colleagues use Eclipse. Adding -imacros in QMAKE_CXXFLAGS has no effect on code completion. In Eclipse you can set it on this screen: http://imgur.com/a/AVFMO Is there a similar setting in Qt Creator? Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: From gotschmarcel at icloud.com Thu May 18 15:55:06 2017 From: gotschmarcel at icloud.com (Marcel Gotsch) Date: Thu, 18 May 2017 15:55:06 +0200 Subject: [Qt-creator] Plugin depend on Qt Creator build Message-ID: <4243E64F-B72B-47C8-B969-65797854AE47@icloud.com> Hello, I’m building a plugin for the Qt Creator and cannot figure out how to get qmake to depend on the Qt Creator target. I want that the Qt Creator target is automatically build before the plugin is build. The qtcreator.pri seems to be included by the qtcreatorplugin.pri, so the target should be available. Another question that comes up is how the plugin can be distributed to users. I have some people that would like to use the plugin, but currently they would have to build the plugin themselves. Also, are they required to use same Qt Creator source code version as their installed Qt Creator has? Any help is really appreciated :) Best, — Marcel Gotsch [gotschmarcel at me.com] [GPG Fingerprint: AF4A 7075 D67D 8C40 2A4C 922C AF89 A4BA 0677 6C16] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: From orgads at gmail.com Wed May 24 19:49:00 2017 From: orgads at gmail.com (Orgad Shaneh) Date: Wed, 24 May 2017 20:49:00 +0300 Subject: [Qt-creator] Qt Creator predefined macro file In-Reply-To: References: Message-ID: Try this: PRECOMPILED_HEADER = your_header.h CONFIG -= precompile_header # prevent actually passing it to the compiler (it is configured by default on Windows) בתאריך 24 במאי 2017 18:32,‏ "Ádám Balázs" כתב: > Hi, > > Our project has a predefined macro file that is given to the compiler > (GCC/Clang) with the -imacros flag. It contains the platform specific > macros so it is a complicated and long file. Can I specify a predefined > macro file in Qt Creator because without it the code completion fails? I > know that I can specify my macros in the DEFINES section of the .pro file > but we have them in a standalone file. It is not possible to move them into > the .pro file because other colleagues use Eclipse. Adding -imacros in > QMAKE_CXXFLAGS has no effect on code completion. > In Eclipse you can set it on this screen: http://imgur.com/a/AVFMO > Is there a similar setting in Qt Creator? > > Adam > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carel.combrink at gmail.com Fri May 26 10:46:35 2017 From: carel.combrink at gmail.com (Carel Combrink) Date: Fri, 26 May 2017 10:46:35 +0200 Subject: [Qt-creator] C++14 Digit Separators issue in Qt Creator Message-ID: Hi All, I have requested QTCREATORBUG-14939 to be reopened since the behavior around C++14 Digit separators is less than ideal. For more information see the comment that I added. Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Fri May 26 12:19:08 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 26 May 2017 12:19:08 +0200 Subject: [Qt-creator] Difference between QtC tarballs from github and qt.io Message-ID: Hi, I noticed there is a difference between tarball from https://github.com/qtproject/qt-creator/archive/v4.3.0.tar.gz and https://download.qt.io/official_releases/qtcreator/4.3/4.3.0/qt-creator-opensource-src-4.3.0.tar.gz namely, "src/shared/qbs" is empty in tarball from github, but it is present in tarball from qt.io Is this intentional? The lack of qbs source in github's tarball bit me yesterday, when I was trying to compile QtC against system-wide qbs installation. It turns out I have to add DEFINES+=QBS_ENABLE_PROJECT_FILE_UPDATES to qmake's command line when generating Makefile for QtC. This is required so that declarations from "qbs/api/project.h": #ifdef QBS_ENABLE_PROJECT_FILE_UPDATES ErrorInfo addGroup(const ProductData &product, const QString &groupName); ErrorInfo addFiles(const ProductData &product, const GroupData &group, const QStringList &filePaths); ErrorInfo removeFiles(const ProductData &product, const GroupData &group, const QStringList &filePaths); ErrorInfo removeGroup(const ProductData &product, const GroupData &group); #endif // QBS_ENABLE_PROJECT_FILE_UPDATES are available when compiling QtC. If I recall correctly, this problem didn't exist when using tarball from qt.io and compiling against system-wide qbs. Am I missing some documentation or is documentation missing something? :-) Thanks! -- Best regards, Andrzej Telszewski From annulen at yandex.ru Fri May 26 12:27:11 2017 From: annulen at yandex.ru (Konstantin Tokarev) Date: Fri, 26 May 2017 13:27:11 +0300 Subject: [Qt-creator] Difference between QtC tarballs from github and qt.io In-Reply-To: References: Message-ID: <2344491495794431@web52j.yandex.ru> 26.05.2017, 13:19, "Andrzej Telszewski" : > Hi, > > I noticed there is a difference between tarball from > https://github.com/qtproject/qt-creator/archive/v4.3.0.tar.gz > > and > https://download.qt.io/official_releases/qtcreator/4.3/4.3.0/qt-creator-opensource-src-4.3.0.tar.gz > > namely, "src/shared/qbs" is empty in tarball from github, but it is > present in tarball from qt.io > > Is this intentional? src/shared/qbs is a submodule, and apparantly Github doesn't include submodules contents into autogenerated archives. Actually, I wouldn't recommend using Github autogenerated archives for any purpose, use official tarballs that have approved contents and good compression. > > The lack of qbs source in github's tarball bit me yesterday, when I was > trying to compile QtC against system-wide qbs installation. > > It turns out I have to add > DEFINES+=QBS_ENABLE_PROJECT_FILE_UPDATES > > to qmake's command line when generating Makefile for QtC. > > This is required so that declarations from "qbs/api/project.h": > #ifdef QBS_ENABLE_PROJECT_FILE_UPDATES >      ErrorInfo addGroup(const ProductData &product, const QString > &groupName); >      ErrorInfo addFiles(const ProductData &product, const GroupData &group, >                         const QStringList &filePaths); >      ErrorInfo removeFiles(const ProductData &product, const GroupData > &group, >                            const QStringList &filePaths); >      ErrorInfo removeGroup(const ProductData &product, const GroupData > &group); > #endif // QBS_ENABLE_PROJECT_FILE_UPDATES > > are available when compiling QtC. > > If I recall correctly, this problem didn't exist when using tarball from > qt.io and compiling against system-wide qbs. > > Am I missing some documentation or is documentation missing something? :-) > > Thanks! > > -- > Best regards, > Andrzej Telszewski > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Regards, Konstantin From mapron at yandex.ru Sun May 28 16:20:11 2017 From: mapron at yandex.ru (mapron) Date: Sun, 28 May 2017 21:20:11 +0700 Subject: [Qt-creator] QtC 4.3 cmake-servermode feature - how to disable that? Message-ID: <530a3231-681c-92f4-6683-3c85db03e35d@yandex.ru> I was happy user of QtC cmake support until update to 4.3.0 release. I have cmake 3.8 (and I don't want to downgrade to 3.6) for my project. After cmake configuration, all project tree is messed up - instead of directory tree with multilevels, I have tons of targets, and pseudo-targets (with no files in list), no logical structure, It's awful! I hadn't find the way how to disable "servermode support", can you help me? This is blocking me from upgrade to 4.3 release. Some information: I have around 200 targets, *2 for cmake object libraries (i cant dissable that), plus 5 cmake targets for each app bundle (~15), It totally messed up! I don't want to see all that (or at lest have multiple level groups like MSVS generator does) From adrenalinedj at gmail.com Sun May 28 18:45:09 2017 From: adrenalinedj at gmail.com (JeremY Larrieu) Date: Sun, 28 May 2017 18:45:09 +0200 Subject: [Qt-creator] Plugin development - Anubis language support In-Reply-To: References: Message-ID: Hello, Did you have some time to take a look to the code I sent ? Thanks in advance. Jeremy 2017-05-03 18:37 GMT+02:00 JeremY Larrieu : > Hello, > > As you can see in the new screenshot attached, the Anubis compiler is auto > detected. > > Here is the code to "auto-detect" kits based on the "auto detected Anubis > toolchains" (it's based on what i found in the android plugin): > > const QList existingKits = Utils::filtered( > ProjectExplorer::KitManager::kits(), [](const ProjectExplorer::Kit *k) { > return k->isAutoDetected(); > }); > QList newKits; > const QList filteredToolchains = > ProjectExplorer::ToolChainManager::toolChains([](const > ProjectExplorer::ToolChain *tc) { > return tc->isAutoDetected() > && tc->isValid() > && tc->typeId() == Constants::AnubisToolchainId; > }); > const QList toolchains = Utils::transform(filteredToolchains, > [](ProjectExplorer::ToolChain *tc) { > return static_cast(tc); > }); > > for (AnubisToolChain *tc : toolchains) { > ProjectExplorer::Kit *newKit = new ProjectExplorer::Kit; > newKit->setAutoDetected(true); > newKit->setAutoDetectionSource("PyramIDEConfiguration"); > > auto findExistingKit = [newKit](const ProjectExplorer::Kit *k) { > return matchKits(newKit, k); }; > ProjectExplorer::Kit *existingKit = Utils::findOrDefault(existingKits, > findExistingKit); > if (existingKit) { > ProjectExplorer::KitManager::deleteKit(newKit); > newKit = existingKit; > } > > auto keys = newKit->allKeys(); > for (Core::Id key : keys) { > qDebug("key => " + key.toString().toLatin1() + " | value => " > + newKit->value(key).toString().toLatin1()); > } > > auto toto = newKit->toHtml(); > qDebug("html:\n" + toto.toLatin1() + "\n"); > > newKit->makeSticky(); > newKit->setUnexpandedDisplayName(QObject::tr("Anubis > %1").arg(tc->compilerVersion())); > > if (!existingKit) > { > ProjectExplorer::KitManager::registerKit(newKit); > } > } > > It's triggered in the plugin entry point (initialize method) on the > "kitsLoaded" signal of KitManager: > connect(KitManager::instance(), &KitManager::kitsLoaded, this, > &PyramIDEPlugin::kitsRestored); > > void PyramIDEPlugin::kitsRestored() > { > PyramIDEConfigurations::updateAutomaticKitList(); > disconnect(KitManager::instance(), &KitManager::kitsChanged, this, > &PyramIDEPlugin::kitsRestored); > } > > Thanks for your help. > > Jeremy > > 2017-05-03 15:14 GMT+02:00 Tobias Hunger : > >> Hi JeremY, >> >> Based on your screenshot: My guess is that Qt Creator does not have any >> compiler defined for your language. >> >> What does the Tool chains tab show? Is there an anubis compiler listed >> there? >> >> Best Regards, >> Tobias > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobias.hunger at gmail.com Mon May 29 11:02:48 2017 From: tobias.hunger at gmail.com (Tobias Hunger) Date: Mon, 29 May 2017 11:02:48 +0200 Subject: [Qt-creator] QtC 4.3 cmake-servermode feature - how to disable that? In-Reply-To: <530a3231-681c-92f4-6683-3c85db03e35d@yandex.ru> References: <530a3231-681c-92f4-6683-3c85db03e35d@yandex.ru> Message-ID: Hi Mapron, Am 28.05.2017 16:20 schrieb "mapron" : I was happy user of QtC cmake support until update to 4.3.0 release. I have cmake 3.8 (and I don't want to downgrade to 3.6) for my project. After cmake configuration, all project tree is messed up - instead of directory tree with multilevels, I have tons of targets, and pseudo-targets (with no files in list), no logical structure, It's awful! I hadn't find the way how to disable "servermode support", can you help me? That is how cmake sees your project:-) The only way I can think of is to use a wrapper script that removes the server mode flag from cmake -E capabilities output. I do plan to remove the non-server-mode support at some point. Probably when most Linux distributions ship with a server-mode enabled cmake binary. This is blocking me from upgrade to 4.3 release. That is unfortunate:-( Some information: I have around 200 targets, *2 for cmake object libraries (i cant dissable that), plus 5 cmake targets for each app bundle (~15), It totally messed up! So what do you want to see? How can I improve the tree for you? I don't want to see all that (or at lest have multiple level groups like MSVS generator does) No idea what MSVS generator does:-( Creator needs a view of how the build system thinks the project is structured. "Project" is that view. We have a lot of people that want a navigation view of the project, which would need to be more configurable:-) I got a bug report for that open for a long time now, but never got around to implement it. Best regards, Tobias _______________________________________________ Qt-creator mailing list Qt-creator at qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator -------------- next part -------------- An HTML attachment was scrubbed... URL: From mapron at yandex.ru Mon May 29 16:33:26 2017 From: mapron at yandex.ru (mapron) Date: Mon, 29 May 2017 21:33:26 +0700 Subject: [Qt-creator] QtC 4.3 cmake-servermode feature - how to disable that? In-Reply-To: References: <530a3231-681c-92f4-6683-3c85db03e35d@yandex.ru> Message-ID: On 29.05.2017 16:02, Tobias Hunger wrote: > Hi Mapron, > > That is how cmake sees your project:-) Fine, but I don't want its point of view :) previous file-view was ok! > > The only way I can think of is to use a wrapper script that removes > the server mode flag from cmake -E capabilities output. Or use patched cmake, or use patched QtC. > > I do plan to remove the non-server-mode support at some point. > Probably when most Linux distributions ship with a server-mode enabled > cmake binary. Such a sad thing. > > This is blocking me from upgrade to 4.3 release. > > > That is unfortunate:-( More unfortunate for you: I've talked to colleagues today, 5 of them uses QtC for development (others MSVS or XCode) - all of them says new view is awful for our project. Such a coincedence... > > Some information: I have around 200 targets, *2 for cmake object > libraries (i cant dissable that), plus 5 cmake targets for each > app bundle (~15), It totally messed up! > > > So what do you want to see? How can I improve the tree for you? Please, leave old file tree view - ok, if you want to move entirely to server-mode - please, make plain file tree available somehow - it would be well acceptable solution! If it can be done, i'll create issue and will collect votes for it :) > > I don't want to see all that (or at lest have multiple level > groups like MSVS generator does) > > > No idea what MSVS generator does:-( Project tree with sub and sub-sub folders, setting with set_target_properties(${target_list} PROPERTIES FOLDER "SomeFolder/SubFolder") > > Creator needs a view of how the build system thinks the project is > structured. "Project" is that view. > > We have a lot of people that want a navigation view of the project, > which would need to be more configurable:-) I got a bug report for > that open for a long time now, but never got around to implement it. > QtC is the best IDE, just do not break it, and it will be fine ;) -------------- next part -------------- An HTML attachment was scrubbed... URL: From wilhelm.meier at fh-kl.de Tue May 30 12:22:10 2017 From: wilhelm.meier at fh-kl.de (Wilhelm) Date: Tue, 30 May 2017 12:22:10 +0200 Subject: [Qt-creator] Using QtC together with simavr Message-ID: <2498f72f-1b1b-1078-7598-b9c73cdbc5df@fh-kl.de> Hi all, I would like to use QtC together with simavr which provides a gdb remote interface. I managed to configure a bare metal device, that connects to a running simavr process on localhost:1234. Debugging works. But: I have to start/stop the simavr manually before/after debugging with QtC. Is there a way to configure a "pre-debug" step (like some sort of deployment) prior to start the debugging in QtC? For bare metal targets there is no chance to actvate a deployment step in QtC. I'm using QtC 4.3.0 Thanks, Wilhelm From wilhelm.meier at fh-kl.de Tue May 30 13:03:14 2017 From: wilhelm.meier at fh-kl.de (Wilhelm) Date: Tue, 30 May 2017 13:03:14 +0200 Subject: [Qt-creator] Using QtC together with simavr In-Reply-To: <2498f72f-1b1b-1078-7598-b9c73cdbc5df@fh-kl.de> References: <2498f72f-1b1b-1078-7598-b9c73cdbc5df@fh-kl.de> Message-ID: I have to modify be statement below: Am 30.05.2017 um 12:22 schrieb Wilhelm: > Hi all, > > I would like to use QtC together with simavr which provides a gdb remote > interface. > > I managed to configure a bare metal device, that connects to a running > simavr process on localhost:1234. Debugging works. The disassembled view doesn't work. I configured the avr-gdb as debugger for the kit used. Any hints? > > But: I have to start/stop the simavr manually before/after debugging > with QtC. Is there a way to configure a "pre-debug" step (like some sort > of deployment) prior to start the debugging in QtC? For bare metal > targets there is no chance to actvate a deployment step in QtC. > > I'm using QtC 4.3.0 > > Thanks, > Wilhelm > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > -- Wilhelm From apoenitz at t-online.de Tue May 30 17:13:28 2017 From: apoenitz at t-online.de (=?iso-8859-1?Q?Andr=E9_P=F6nitz?=) Date: Tue, 30 May 2017 17:13:28 +0200 Subject: [Qt-creator] Using QtC together with simavr In-Reply-To: References: <2498f72f-1b1b-1078-7598-b9c73cdbc5df@fh-kl.de> Message-ID: <20170530151328.GB1415@klara.mpi.htwm.de> On Tue, May 30, 2017 at 01:03:14PM +0200, Wilhelm wrote: > I have to modify be statement below: > > Am 30.05.2017 um 12:22 schrieb Wilhelm: > > Hi all, > > > > I would like to use QtC together with simavr which provides a gdb remote > > interface. > > > > I managed to configure a bare metal device, that connects to a running > > simavr process on localhost:1234. Debugging works. > > The disassembled view doesn't work. I configured the avr-gdb as debugger > for the kit used. > > Any hints? You could paste the debugger log (contents of right pane of Windows ->Views->Debugger Log), or directly create a report on bugreports.qt.io and attach the log there. Andre' From wilhelm.meier at fh-kl.de Wed May 31 11:05:00 2017 From: wilhelm.meier at fh-kl.de (Wilhelm) Date: Wed, 31 May 2017 11:05:00 +0200 Subject: [Qt-creator] Using QtC together with simavr In-Reply-To: <20170530151328.GB1415@klara.mpi.htwm.de> References: <2498f72f-1b1b-1078-7598-b9c73cdbc5df@fh-kl.de> <20170530151328.GB1415@klara.mpi.htwm.de> Message-ID: <336ef5c0-e1e2-4977-1d82-207cc8355167@fh-kl.de> Am 30.05.2017 um 17:13 schrieb André Pönitz: > On Tue, May 30, 2017 at 01:03:14PM +0200, Wilhelm wrote: >> I have to modify be statement below: >> >> Am 30.05.2017 um 12:22 schrieb Wilhelm: >>> Hi all, >>> >>> I would like to use QtC together with simavr which provides a gdb remote >>> interface. >>> >>> I managed to configure a bare metal device, that connects to a running >>> simavr process on localhost:1234. Debugging works. >> >> The disassembled view doesn't work. I configured the avr-gdb as debugger >> for the kit used. >> >> Any hints? > > You could paste the debugger log (contents of right pane of Windows > ->Views->Debugger Log), wHinweis: Dieses Log enhält möglicherweise vertrauliche Informationen über Ihren Computer, Umgebungsvariablen, Speicherinhalte der untersuchten Prozesse und weiteres. Es wird von Qt Creator nie über das Internet übertragen und nur auf der Festplatte gespeichert, wenn Sie die entsprechende Option aus dem Kontextmenü aufrufen, oder durch Abläufe, die Qt Creator nicht beeinflussen kann, bespielsweise Auslagerungsdateien. wSie werden möglicherweise gebeten, den Inhalt dieses Logs mitzuteilen, wenn Sie Fehlfunktionen des Debugger berichten. In diesem Fall achten Sie darauf, dass Ihre Einsendung nur Daten enthält, die Sie weitergeben wollen und dürfen. w sStarte Debugger "GdbEngine" für ABI "unknown-unknown-unknown-unknown-unknown"... dStart parameters: 'src (über GDB-Server oder Hardware-Debugger)' mode: 6 dABI: unknown-unknown-unknown-unknown-unknown dLanguages: c++ dExecutable: /home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.elf dDebugger: /usr/bin/avr-gdb dProject: /home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/srcAddtional Search Directories: dRemote: localhost:1234 dSysroot: dDebug Source Location: dDebugger settings: dUseCodeModel: true (default: true) dUseDebuggingHelper: true (default: true) dStationaryEditorWhileStepping: false (default: false) dRaiseOnInterrupt: true (default: true) dBreakpointsFullPath: false (default: false) dSwitchModeOnExit: false (default: false) dCloseMemoryBuffersOnExit: true (default: true) dCloseBuffersOnExit: false (default: false) dLogTimeStamps: false (default: false) dAutoQuit: false (default: false) dUseMessageBoxForSignals: true (default: true) dFontSizeFollowsEditor: false (default: false) dUseAlternatingRowColours: false (default: false) dBreakOnCrtDbgReport: false (default: false) dBreakEvent: (default: ) dSourcePaths: (default: ) dSymbolPaths: (default: ) dAdditionalArguments: (default: ) dGdbCustomDumperCommands: (default: ) dExtraDumperFile: (default: ) dAlwaysAdjustColumnWidths: true (default: true) dUseAddressInStackView: false (default: false) dUseAddressInBreakpointsView: false (default: false) dUseToolTipsInBreakpointsView: false (default: true) *** dUseToolTipsInBreakpointsView: false (default: false) dUseToolTipsInLocalsView: false (default: false) dUseToolTips: true (default: true) dShowThreadNames: false (default: false) dIdentifyDebugInfoPackages: false (default: false) dIntelFlavor: false (default: false) dMultiInferior: true (default: false) *** dWarnOnReleaseBuilds: true (default: true) dTargetAsync: false (default: false) dUseDynamicType: true (default: true) dAutoEnrichParameters: true (default: true) dWatchdogTimeout: 20 (default: 20) dGdbPostAttachCommands: (default: ) dGdbStartupCommands: (default: ) dLoadGdbDumpers2: false (default: false) dLoadGdbInit: true (default: true) dIgnoreFirstChanceAccessViolation: false (default: false) dUsePythonDumper: true (default: true) dBreakpointCorrection: true (default: true) dCDB_Console: false (default: false) dAdjustBreakpointLocations: true (default: true) dSelectedPluginBreakpoints: false (default: false) dAllPluginBreakpoints: true (default: true) dEnableReverseDebugging: false (default: false) dSkipKnownFrames: false (default: false) dDisplayStringLimit: 100 (default: 100) dMaximalStringLength: 10000 (default: 10000) dAutoDerefPointers: true (default: true) dSortStructMembers: true (default: true) dShowQObjectNames2: true (default: true) dShowQtNamespace: true (default: true) dShowStandardNamespace: true (default: true) dMaximalStackDepth: 20 (default: 20) dQmlInspector.ShowAppOnTop: false (default: false) dShowQmlObjectTree: false (default: true) *** dBreakOnAbort: false (default: false) dBreakOnFatal: false (default: false) dBreakOnWarning: false (default: false) dBreakOnCatch: false (default: false) dBreakOnThrow: false (default: false) dSelectedPluginBreakpointsPattern: .* (default: .*) dNoPluginBreakpoints: false (default: false) dState changed from DebuggerNotReady(0) to EngineSetupRequested(1) [master] dQUEUE: SETUP ENGINE dCALL: SETUP ENGINE dTRYING TO START ADAPTER dENABLING TEST CASE: 0 dSTARTING /usr/bin/avr-gdb -i mi dGDB STARTED, INITIALIZING IT <1show version <2show debug-file-directory <3set print object on <4set breakpoint pending on <5set print elements 10000 <6set unwindonsignal on <7set width 0 <8set height 0 sBereite zu debuggenden Prozess vor... <9set detach-on-fork off <10python sys.path.insert(1, '/usr/share/qtcreator/debugger/') <11python sys.path.append('/usr/bin/data-directory/python') <12python from gdbbridge import * <13python theDumper.loadDumpers({"token":13}) >=thread-group-added,id="i1" >~"GNU gdb (GDB) 7.12.1\n" >~"Copyright (C) 2017 Free Software Foundation, Inc.\n" >~"License GPLv3+: GNU GPL version 3 or later \nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \"show copying\"\nand \"show warranty\" for details.\n" >~"This GDB was configured as \"--host=x86_64-pc-linux-gnu --target=avr\".\nType \"show configuration\" for configuration details." >~"\nFor bug reporting instructions, please see:\n" >~".\n" >~"Find the GDB manual and other documentation resources online at:\n.\n" >~"For help, type \"help\".\n" >~"Type \"apropos word\" to search for commands related to \"word\".\n" >&"show version\n" >~"GNU gdb (GDB) 7.12.1\n" >~"Copyright (C) 2017 Free Software Foundation, Inc.\n" >~"License GPLv3+: GNU GPL version 3 or later \nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \"show copying\"\nand \"show warranty\" for details.\n" >~"This GDB was configured as \"--host=x86_64-pc-linux-gnu --target=avr\".\nType \"show configuration\" for configuration details." >~"\nFor bug reporting instructions, please see:\n" >~".\n" >~"Find the GDB manual and other documentation resources online at:\n.\n" >~"For help, type \"help\".\n" >~"Type \"apropos word\" to search for commands related to \"word\".\n" >1^done dPARSING VERSION: 1^done dSUPPORTED GDB VERSION GNU gdb (GDB) 7.12.1 dCopyright (C) 2017 Free Software Foundation, Inc. dLicense GPLv3+: GNU GPL version 3 or later dThis is free software: you are free to change and redistribute it. dThere is NO WARRANTY, to the extent permitted by law. Type "show copying" dand "show warranty" for details. dThis GDB was configured as "--host=x86_64-pc-linux-gnu --target=avr". dType "show configuration" for configuration details. dFor bug reporting instructions, please see: d. dFind the GDB manual and other documentation resources online at: d. dFor help, type "help". dType "apropos word" to search for commands related to "word". dGNU gdb (GDB) 7.12.1 dCopyright (C) 2017 Free Software Foundation, Inc. dLicense GPLv3+: GNU GPL version 3 or later dThis is free software: you are free to change and redistribute it. dThere is NO WARRANTY, to the extent permitted by law. Type "show copying" dand "show warranty" for details. dThis GDB was configured as "--host=x86_64-pc-linux-gnu --target=avr". dType "show configuration" for configuration details. dFor bug reporting instructions, please see: d. dFind the GDB manual and other documentation resources online at: d. dFor help, type "help". dType "apropos word" to search for commands related to "word". dUSING GDB VERSION: 71201, BUILD: 2017 <14-interpreter-exec console "set target-async off" >&"show debug-file-directory\n" >~"The directory where separate debug symbols are searched for is \"/usr/lib/debug\".\n" >2^done >&"set print object on\n" >=cmd-param-changed,param="print object",value="on" >3^done >&"set breakpoint pending on\n" >=cmd-param-changed,param="breakpoint pending",value="on" >4^done >&"set print elements 10000\n" >=cmd-param-changed,param="print elements",value="10000" >5^done >&"set unwindonsignal on\n" >=cmd-param-changed,param="unwindonsignal",value="on" >6^done >&"set width 0\n" >=cmd-param-changed,param="width",value="4294967295" >7^done >&"set height 0\n" >8^done >&"set detach-on-fork off\n" >=cmd-param-changed,param="detach-on-fork",value="off" >9^done >&"python sys.path.insert(1, '/usr/share/qtcreator/debugger/')\n" >10^done >&"python sys.path.append('/usr/bin/data-directory/python')\n" >11^done >&"python from gdbbridge import *\n" >12^done >&"python theDumper.loadDumpers({\"token\":13})\n" >~"result={token=\"13\",dumpers=[{type=\"QVariant (QVariantMap)\",formats=\"17\"},{type=\"QAtomicInt\"},{type=\"QBasicAtomicInt\"},{type=\"QAtomicPointer\"},{type=\"QByteArray\",formats=\"5, 6, 7, 8\"},{type=\"QArrayData\"},{type=\"QByteArrayData\"},{type=\"QBitArray\"},{type=\"QChar\"},{type=\"Qt__ItemDataRole\"},{type=\"QStandardItemData\"},{type=\"QStandardItem\"},{type=\"QDate\"},{type=\"QTime\"},{type=\"QTimeZone\"},{type=\"QDateTime\"},{type=\"QDir\"},{type=\"QFile\"},{type=\"QFileInfo\"},{type=\"QFixed\"},{type=\"QFiniteStack\",formats=\"16\"},{type=\"QFlags\"},{type=\"QHash\",formats=\"17\"},{type=\"QVariantHash\"},{type=\"QHashNode\",formats=\"17\"},{type=\"QHash__const_iterator\"},{type=\"QHash__iterator\"},{type=\"QHostAddress\"},{type=\"QIPv6Address\"},{type=\"QList\",formats=\"18, 19\"},{type=\"QVariantList\"},{type=\"QImage\",formats=\"2, 4\"},{type=\"QLinkedList\"},{type=\"QLocale\"},{type=\"QMapNode\"},{type=\"QMap\",formats=\"17\"},{type=\"QMultiMap\",formats=\"17\"},{type=\"QVariantMap\",formats=\"17\"},{type=\"QMetaMethod\"},{type=\"QMetaEnum\"},{type=\"QMetaProperty\"},{type=\"QMetaClassInfo\"},{type=\"QMetaObject\"},{type=\"QObjectPrivate__ConnectionList\"},{type=\"QPixmap\"},{type=\"QPoint\"},{type=\"QPointF\"},{type=\"QRect\"},{type=\"QRectF\"},{type=\"QRegExp\"},{type=\"QRegion\"},{type=\"QScopedPointer\"},{type=\"QSet\"},{type=\"QSharedData\"},{type=\"QSharedDataPointer\"},{type=\"QSize\"},{type=\"QSizeF\"},{type=\"QStack\",formats=\"16\"},{type=\"QPolygonF\"},{type=\"QPolygon\"},{type=\"QGraphicsPolygonItem\"},{type=\"QString\",editable=\"true\",formats=\"2, 4\"},{type=\"QStaticStringData\"},{type=\"QTypedArrayData\"},{type=\"QStringData\"},{type=\"QHashedString\"},{type=\"QQmlRefCount\"},{type=\"QStringRef\"},{type=\"QStringList\"},{type=\"QTemporaryFile\"},{type=\"QTextCodec\"},{type=\"QTextCursor\"},{type=\"QTextDocument\"},{type=\"QUrl\",formats=\"2, 4\"},{type=\"QUuid\"},{type=\"QVariant\"},{type=\"QVector\",editable=\"true\",formats=\"16\"},{type=\"QVarLengthArray\"},{type=\"QSharedPointer\"},{type=\"QWeakPointer\"},{type=\"QXmlAttributes__Attribute\"},{type=\"QXmlAttributes\"},{type=\"QXmlStreamStringRef\"},{type=\"QXmlStreamAttribute\"},{type=\"QV4__Heap__Base\"},{type=\"QV4__Heap__String\"},{type=\"QV4__Object\"},{type=\"QV4__FunctionObject\"},{type=\"QV4__CompilationUnit\"},{type=\"QV4__CallContext\"},{type=\"QV4__ScriptFunction\"},{type=\"QV4__SimpleScriptFunction\"},{type=\"QV4__ExecutionContext\"},{type=\"QQmlSourceLocation\"},{type=\"QV4__String\"},{type=\"QV4__Identifier\"},{type=\"QV4__PropertyHash\"},{type=\"QV4__InternalClass__Transition\"},{type=\"QV4__InternalClassTransition\"},{type=\"QV4__SharedInternalClassData\"},{type=\"QV4__IdentifierTable\"},{type=\"QV4_Object\"},{type=\"QV4__Value\"},{type=\"QV__PropertyHashData\"},{type=\"QV__PropertyHash\"},{type=\"QV4__Scoped\"},{type=\"QV4__ScopedString\"},{type=\"QJSValue\"},{type=\"QQmlBinding\"},{type=\"QTJSC__JSValue\"},{type=\"QScriptValue\"},{type=\"QQmlAccessorProperties__Properties\"},{type=\"QJsonPrivate__qle_bitfield\"},{type=\"QJsonPrivate__qle_signedbitfield\"},{type=\"QJsonPrivate__q_littleendian\"},{type=\"QJsonValue\"},{type=\"QJsonArray\"},{type=\"QJsonObject\"},{type=\"QSqlResultPrivate\"},{type=\"QSqlField\"},{type=\"QLazilyAllocated\"},{type=\"qfloat16\"},{type=\"std__array\",formats=\"16\"},{type=\"std____1__array\",formats=\"16\"},{type=\"std__complex\"},{type=\"std____1__complex\"},{type=\"std__deque\"},{type=\"std____1__deque\"},{type=\"std__deque__QNX\"},{type=\"std__deque__MSVC\"},{type=\"std____debug__deque\"},{type=\"std__list\"},{type=\"std__list__QNX\"},{type=\"std____debug__list\"},{type=\"std____cxx11__list\"},{type=\"std____1__list\"},{type=\"std__map\",formats=\"17\"},{type=\"std____debug__map\"},{type=\"std____debug__set\"},{type=\"std__multiset\"},{type=\"std____cxx1998__map\"},{type=\"std__multimap\",formats=\"17\"},{type=\"std___Rb_tree_iterator\"},{type=\"std___Rb_tree_const_iterator\"},{type=\"std__map__iterator\"},{type=\"__gnu_debug___Safe_iterator\"},{type=\"std__map__const_iterator\"},{type=\"std__set__iterator\"},{type=\"std__set__const_iterator\"},{type=\"std____cxx1998__set\"},{type=\"std___Tree_const_iterator\"},{type=\"std___Tree_iterator\"},{type=\"std__set\"},{type=\"std__set__QNX\"},{type=\"std____1__set\"},{type=\"std____1__multiset\"},{type=\"std____1__map\",formats=\"17\"},{type=\"std____1__multimap\",formats=\"17\"},{type=\"std____1__map__iterator\"},{type=\"std____1__map__const_iterator\"},{type=\"std____1__set__iterator\"},{type=\"std____1__set_const_iterator\"},{type=\"std__stack\"},{type=\"std____debug__stack\"},{type=\"std____1__stack\"},{type=\"std__string\",editable=\"true\",formats=\"5, 6, 7, 8\"},{type=\"std____1__string\"},{type=\"std____1__wstring\"},{type=\"std____weak_ptr\"},{type=\"std__weak_ptr\"},{type=\"std____1__weak_ptr\"},{type=\"std__shared_ptr\"},{type=\"std____1__shared_ptr\"},{type=\"std__unique_ptr\"},{type=\"std____1__unique_ptr\"},{type=\"std__pair\"},{type=\"std__unordered_map\",formats=\"17\"},{type=\"std____debug__unordered_map\",formats=\"17\"},{type=\"std__unordered_multimap\",formats=\"17\"},{type=\"std____debug__unordered_multimap\",formats=\"17\"},{type=\"std__unordered_set\"},{type=\"std____1__unordered_map\",formats=\"17\"},{type=\"std____1__unordered_set\"},{type=\"std____debug__unordered_set\"},{type=\"std__unordered_multiset\"},{type=\"std____debug__unordered_multiset\"},{type=\"std__valarray\",formats=\"16\"},{type=\"std____1__valarray\",formats=\"16\"},{type=\"std__vector\",editable=\"true\",formats=\"16\"},{type=\"std____1__vector\"},{type=\"std____debug__vector\",formats=\"16\"},{type=\"string\",editable=\"true\"},{type=\"std__wstring\",formats=\"2, 4\"},{type=\"std__basic_string\"},{type=\"std____cxx11__basic_string\"},{type=\"std____cxx11__string\",formats=\"5, 6, 7, 8\"},{type=\"std____cxx11__wstring\",formats=\"2, 4\"},{type=\"std____1__basic_string\"},{type=\"wstring\"},{type=\"std____1__once_flag\"},{type=\"std__once_flag\"},{type=\"__gnu_cxx__hash_set\"},{type=\"uint8_t\"},{type=\"int8_t\"},{type=\"__m128\"},{type=\"__m256\"},{type=\"__m512\"},{type=\"__m128d\"},{type=\"__m256d\"},{type=\"__m512d\"},{type=\"__m128i\"},{type=\"__m256i\"},{type=\"__m512i\"},{type=\"Eigen__Matrix\"},{type=\"NimStringDesc\"},{type=\"NimGenericSequence__\"},{type=\"TNimNode\"},{type=\"KDSoapValue1\"},{type=\"KDSoapValue\"},{type=\"WTF__String\"},{type=\"QtcDumperTest_FieldAccessByIndex\"},{type=\"QtcDumperTest_PointerArray\"},{type=\"QtcDumperTest_BufArray\"},{type=\"boost__bimaps__bimap\"},{type=\"boost__optional\"},{type=\"boost__shared_ptr\"},{type=\"boost__container__list\"},{type=\"boost__gregorian__date\"},{type=\"boost__posix_time__ptime\"},{type=\"boost__posix_time__time_duration\"},{type=\"boost__unordered__unordered_set\"},{type=\"boost__variant\"},{type=\"cv__Size_\"},{type=\"cv__Mat\",formats=\"4\"},{type=\"Core__Id\"},{type=\"Debugger__Internal__GdbMi\"},{type=\"Debugger__Internal__DisassemblerLine\"},{type=\"Debugger__Internal__WatchData\"},{type=\"Debugger__Internal__WatchItem\"},{type=\"Debugger__Internal__BreakpointModelId\"},{type=\"Debugger__Internal__ThreadId\"},{type=\"CPlusPlus__ByteArrayRef\"},{type=\"CPlusPlus__Identifier\"},{type=\"CPlusPlus__Symbol\"},{type=\"CPlusPlus__Class\"},{type=\"CPlusPlus__IntegerType\"},{type=\"CPlusPlus__FullySpecifiedType\"},{type=\"CPlusPlus__NamedType\"},{type=\"CPlusPlus__PointerType\"},{type=\"CPlusPlus__TemplateNameId\"},{type=\"CPlusPlus__QualifiedNameId\"},{type=\"CPlusPlus__Literal\"},{type=\"CPlusPlus__StringLiteral\"},{type=\"CPlusPlus__Internal__Value\"},{type=\"Utils__FileName\"},{type=\"Utils__ElfSection\"},{type=\"Utf8String\"},{type=\"CPlusPlus__Token\"},{type=\"CPlusPlus__Internal__PPToken\"},{type=\"ProString\"},{type=\"ProKey\"},{type=\"Core__GeneratedFile\"},{type=\"ProjectExplorer__Node\"},{type=\"ProjectExplorer__FolderNode\"},{type=\"ProjectExplorer__ProjectNode\"},{type=\"CMakeProjectManager__Internal__CMakeProjectNode\"},{type=\"QmakeProjectManager__QmakePriFileNode\"},{type=\"QmakeProjectManager__QmakeProFileNode\"},],python=\"30601\"}\n" >13^done dENGINE SUCCESSFULLY STARTED dNOTE: ENGINE SETUP OK dState changed from EngineSetupRequested(1) to EngineSetupOk(3) [master] dQUEUE: SETUP INFERIOR dState changed from EngineSetupOk(3) to InferiorSetupRequested(4) [master] dQUEUE: SETUP INFERIOR >14^done dCALL: SETUP INFERIOR <15unset environment CASROOT <16unset environment CSF_EXCEPTION_PROMPT <17unset environment CSF_GraphicShr <18unset environment CSF_IGESDefaults <19unset environment CSF_LANGUAGE <20unset environment CSF_MDTVTexturesDirectory <21unset environment CSF_PluginDefaults <22unset environment CSF_SHMessage <23unset environment CSF_STEPDefaults <24unset environment CSF_StandardDefaults <25unset environment CSF_StandardLiteDefaults <26unset environment CSF_UnitsDefinition <27unset environment CSF_UnitsLexicon <28unset environment CSF_XCAFDefaults <29unset environment CSF_XSMessage <30unset environment CSF_XmlOcafResource <31unset environment DBUS_SESSION_BUS_ADDRESS <32unset environment DESKTOP_SESSION <33unset environment DISPLAY <34unset environment GS_LIB <35unset environment GTK_MODULES <36unset environment HG <37unset environment HOME <38unset environment KDE_FULL_SESSION <39unset environment KDE_SESSION_UID <40unset environment KDE_SESSION_VERSION <41unset environment LANG <42unset environment LANGUAGE <43unset environment LARCH_PATH <44unset environment LCLIMPORTDIR <45unset environment LD_LIBRARY_PATH <46unset environment LOGNAME <47unset environment MAIL <48unset environment MMGT_CLEAR <49unset environment MOZ_PLUGIN_PATH <50unset environment PATH <51unset environment PWD <52unset environment QSG_RENDER_LOOP <53unset environment QT_AUTO_SCREEN_SCALE_FACTOR <54unset environment QT_LOGGING_TO_CONSOLE <55unset environment SESSION_MANAGER <56unset environment SHELL <57unset environment SHLVL <58unset environment USER <59unset environment XAUTHORITY <60unset environment XCURSOR_THEME <61unset environment XDG_CURRENT_DESKTOP <62unset environment XDG_DATA_DIRS <63unset environment XDG_RUNTIME_DIR <64unset environment XDG_SEAT <65unset environment XDG_SEAT_PATH <66unset environment XDG_SESSION_CLASS <67unset environment XDG_SESSION_DESKTOP <68unset environment XDG_SESSION_ID <69unset environment XDG_SESSION_PATH <70unset environment XDG_SESSION_TYPE <71unset environment XDG_VTNR <72unset environment _ <73-file-exec-and-symbols "/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.elf" >&"unset environment CASROOT\n" >15^done >&"unset environment CSF_EXCEPTION_PROMPT\n" >16^done >&"unset environment CSF_GraphicShr\n" >17^done >&"unset environment CSF_IGESDefaults\n" >18^done >&"unset environment CSF_LANGUAGE\n" >19^done >&"unset environment CSF_MDTVTexturesDirectory\n" >20^done >&"unset environment CSF_PluginDefaults\n" >21^done >&"unset environment CSF_SHMessage\n" >22^done >&"unset environment CSF_STEPDefaults\n" >23^done >&"unset environment CSF_StandardDefaults\n" >24^done >&"unset environment CSF_StandardLiteDefaults\n" >25^done >&"unset environment CSF_UnitsDefinition\n" >26^done >&"unset environment CSF_UnitsLexicon\n" >27^done >&"unset environment CSF_XCAFDefaults\n" >28^done >&"unset environment CSF_XSMessage\n" >29^done >&"unset environment CSF_XmlOcafResource\n" >30^done >&"unset environment DBUS_SESSION_BUS_ADDRESS\n" >31^done >&"unset environment DESKTOP_SESSION\n" >32^done >&"unset environment DISPLAY\n" >33^done >&"unset environment GS_LIB\n" >34^done >&"unset environment GTK_MODULES\n" >35^done >&"unset environment HG\n" >36^done >&"unset environment HOME\n" >37^done >&"unset environment KDE_FULL_SESSION\n" >38^done >&"unset environment KDE_SESSION_UID\n" >39^done >&"unset environment KDE_SESSION_VERSION\n" >40^done >&"unset environment LANG\n" >41^done >&"unset environment LANGUAGE\n" >42^done >&"unset environment LARCH_PATH\n" >43^done >&"unset environment LCLIMPORTDIR\n" >44^done >&"unset environment LD_LIBRARY_PATH\n" >45^done >&"unset environment LOGNAME\n" >46^done >&"unset environment MAIL\n" >47^done >&"unset environment MMGT_CLEAR\n" >48^done >&"unset environment MOZ_PLUGIN_PATH\n" >49^done >&"unset environment PATH\n" >50^done >&"unset environment PWD\n" >51^done >&"unset environment QSG_RENDER_LOOP\n" >52^done >&"unset environment QT_AUTO_SCREEN_SCALE_FACTOR\n" >53^done >&"unset environment QT_LOGGING_TO_CONSOLE\n" >54^done >&"unset environment SESSION_MANAGER\n" >55^done >&"unset environment SHELL\n" >56^done >&"unset environment SHLVL\n" >57^done >&"unset environment USER\n" >58^done >&"unset environment XAUTHORITY\n" >59^done >&"unset environment XCURSOR_THEME\n" >60^done >&"unset environment XDG_CURRENT_DESKTOP\n" >61^done >&"unset environment XDG_DATA_DIRS\n" >62^done >&"unset environment XDG_RUNTIME_DIR\n" >63^done >&"unset environment XDG_SEAT\n" >64^done >&"unset environment XDG_SEAT_PATH\n" >65^done >&"unset environment XDG_SESSION_CLASS\n" >66^done >&"unset environment XDG_SESSION_DESKTOP\n" >67^done >&"unset environment XDG_SESSION_ID\n" >68^done >&"unset environment XDG_SESSION_PATH\n" >69^done >&"unset environment XDG_SESSION_TYPE\n" >70^done >&"unset environment XDG_VTNR\n" >71^done >&"unset environment _\n" >72^done >73^done <74target remote tcp:localhost:1234 >&"target remote tcp:localhost:1234\n" >&"tcp:localhost:1234: Die Wartezeit f\303\274r die Verbindung ist abgelaufen.\n" >74^error,msg="tcp:localhost:1234: Die Wartezeit f\303\274r die Verbindung ist abgelaufen." sDie Anwendung konnte nicht gestartet werden: Die Verbindung zum Server konnte nicht hergestellt werden: stcp:localhost:1234: Die Wartezeit für die Verbindung ist abgelaufen. dINFERIOR START FAILED dNOTE: INFERIOR SETUP FAILED sDie Initialisierung schlug fehl. dState changed from InferiorSetupRequested(4) to InferiorSetupFailed(5) [master] dState changed from InferiorSetupFailed(5) to EngineShutdownRequested(19) [master] dQUEUE: SHUTDOWN ENGINE dCALL: SHUTDOWN ENGINE dINITIATE GDBENGINE SHUTDOWN IN STATE 0, PROC: 2 <75python theDumper.exitGdb({"token":75}) >&"python theDumper.exitGdb({\"token\":75})\n" dGDB PROCESS FINISHED, status 0, exit code 0 dNOTE: ENGINE SHUTDOWN OK dState changed from EngineShutdownRequested(19) to EngineShutdownOk(21) [master] dState changed from EngineShutdownOk(21) to DebuggerFinished(22) [master] dQUEUE: FINISH DEBUGGER dNOTE: FINISH DEBUGGER dHANDLE RUNCONTROL FINISHED sDebuggen beendet. sStarte Debugger "GdbEngine" für ABI "unknown-unknown-unknown-unknown-unknown"... dStart parameters: 'src (über GDB-Server oder Hardware-Debugger)' mode: 6 dABI: unknown-unknown-unknown-unknown-unknown dLanguages: c++ dExecutable: /home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.elf dDebugger: /usr/bin/avr-gdb dProject: /home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/srcAddtional Search Directories: dRemote: localhost:1234 dSysroot: dDebug Source Location: dDebugger settings: dUseCodeModel: true (default: true) dUseDebuggingHelper: true (default: true) dStationaryEditorWhileStepping: false (default: false) dRaiseOnInterrupt: true (default: true) dBreakpointsFullPath: false (default: false) dSwitchModeOnExit: false (default: false) dCloseMemoryBuffersOnExit: true (default: true) dCloseBuffersOnExit: false (default: false) dLogTimeStamps: false (default: false) dAutoQuit: false (default: false) dUseMessageBoxForSignals: true (default: true) dFontSizeFollowsEditor: false (default: false) dUseAlternatingRowColours: false (default: false) dBreakOnCrtDbgReport: false (default: false) dBreakEvent: (default: ) dSourcePaths: (default: ) dSymbolPaths: (default: ) dAdditionalArguments: (default: ) dGdbCustomDumperCommands: (default: ) dExtraDumperFile: (default: ) dAlwaysAdjustColumnWidths: true (default: true) dUseAddressInStackView: false (default: false) dUseAddressInBreakpointsView: false (default: false) dUseToolTipsInBreakpointsView: false (default: true) *** dUseToolTipsInBreakpointsView: false (default: false) dUseToolTipsInLocalsView: false (default: false) dUseToolTips: true (default: true) dShowThreadNames: false (default: false) dIdentifyDebugInfoPackages: false (default: false) dIntelFlavor: false (default: false) dMultiInferior: true (default: false) *** dWarnOnReleaseBuilds: true (default: true) dTargetAsync: false (default: false) dUseDynamicType: true (default: true) dAutoEnrichParameters: true (default: true) dWatchdogTimeout: 20 (default: 20) dGdbPostAttachCommands: (default: ) dGdbStartupCommands: (default: ) dLoadGdbDumpers2: false (default: false) dLoadGdbInit: true (default: true) dIgnoreFirstChanceAccessViolation: false (default: false) dUsePythonDumper: true (default: true) dBreakpointCorrection: true (default: true) dCDB_Console: false (default: false) dAdjustBreakpointLocations: true (default: true) dSelectedPluginBreakpoints: false (default: false) dAllPluginBreakpoints: true (default: true) dEnableReverseDebugging: false (default: false) dSkipKnownFrames: false (default: false) dDisplayStringLimit: 100 (default: 100) dMaximalStringLength: 10000 (default: 10000) dAutoDerefPointers: true (default: true) dSortStructMembers: true (default: true) dShowQObjectNames2: true (default: true) dShowQtNamespace: true (default: true) dShowStandardNamespace: true (default: true) dMaximalStackDepth: 20 (default: 20) dQmlInspector.ShowAppOnTop: false (default: false) dShowQmlObjectTree: false (default: true) *** dBreakOnAbort: false (default: false) dBreakOnFatal: false (default: false) dBreakOnWarning: false (default: false) dBreakOnCatch: false (default: false) dBreakOnThrow: false (default: false) dSelectedPluginBreakpointsPattern: .* (default: .*) dNoPluginBreakpoints: false (default: false) dState changed from DebuggerNotReady(0) to EngineSetupRequested(1) [master] dQUEUE: SETUP ENGINE dCALL: SETUP ENGINE dTRYING TO START ADAPTER dENABLING TEST CASE: 0 dSTARTING /usr/bin/avr-gdb -i mi dGDB STARTED, INITIALIZING IT <76show version <77show debug-file-directory <78set print object on <79set breakpoint pending on <80set print elements 10000 <81set unwindonsignal on <82set width 0 <83set height 0 sBereite zu debuggenden Prozess vor... <84set detach-on-fork off <85python sys.path.insert(1, '/usr/share/qtcreator/debugger/') <86python sys.path.append('/usr/bin/data-directory/python') <87python from gdbbridge import * <88python theDumper.loadDumpers({"token":88}) >=thread-group-added,id="i1" >~"GNU gdb (GDB) 7.12.1\n" >~"Copyright (C) 2017 Free Software Foundation, Inc.\n" >~"License GPLv3+: GNU GPL version 3 or later \nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \"show copying\"\nand \"show warranty\" for details.\n" >~"This GDB was configured as \"--host=x86_64-pc-linux-gnu --target=avr\".\nType \"show configuration\" for configuration details." >~"\nFor bug reporting instructions, please see:\n" >~".\n" >~"Find the GDB manual and other documentation resources online at:\n.\n" >~"For help, type \"help\".\n" >~"Type \"apropos word\" to search for commands related to \"word\".\n" >&"show version\n" >~"GNU gdb (GDB) 7.12.1\n" >~"Copyright (C) 2017 Free Software Foundation, Inc.\n" >~"License GPLv3+: GNU GPL version 3 or later \nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \"show copying\"\nand \"show warranty\" for details.\n" >~"This GDB was configured as \"--host=x86_64-pc-linux-gnu --target=avr\".\nType \"show configuration\" for configuration details." >~"\nFor bug reporting instructions, please see:\n" >~".\n" >~"Find the GDB manual and other documentation resources online at:\n.\n" >~"For help, type \"help\".\n" >~"Type \"apropos word\" to search for commands related to \"word\".\n" >76^done dPARSING VERSION: 76^done dSUPPORTED GDB VERSION GNU gdb (GDB) 7.12.1 dCopyright (C) 2017 Free Software Foundation, Inc. dLicense GPLv3+: GNU GPL version 3 or later dThis is free software: you are free to change and redistribute it. dThere is NO WARRANTY, to the extent permitted by law. Type "show copying" dand "show warranty" for details. dThis GDB was configured as "--host=x86_64-pc-linux-gnu --target=avr". dType "show configuration" for configuration details. dFor bug reporting instructions, please see: d. dFind the GDB manual and other documentation resources online at: d. dFor help, type "help". dType "apropos word" to search for commands related to "word". dGNU gdb (GDB) 7.12.1 dCopyright (C) 2017 Free Software Foundation, Inc. dLicense GPLv3+: GNU GPL version 3 or later dThis is free software: you are free to change and redistribute it. dThere is NO WARRANTY, to the extent permitted by law. Type "show copying" dand "show warranty" for details. dThis GDB was configured as "--host=x86_64-pc-linux-gnu --target=avr". dType "show configuration" for configuration details. dFor bug reporting instructions, please see: d. dFind the GDB manual and other documentation resources online at: d. dFor help, type "help". dType "apropos word" to search for commands related to "word". dUSING GDB VERSION: 71201, BUILD: 2017 <89-interpreter-exec console "set target-async off" >&"show debug-file-directory\n" >~"The directory where separate debug symbols are searched for is \"/usr/lib/debug\".\n" >77^done >&"set print object on\n" >=cmd-param-changed,param="print object",value="on" >78^done >&"set breakpoint pending on\n" >=cmd-param-changed,param="breakpoint pending",value="on" >79^done >&"set print elements 10000\n" >=cmd-param-changed,param="print elements",value="10000" >80^done >&"set unwindonsignal on\n" >=cmd-param-changed,param="unwindonsignal",value="on" >81^done >&"set width 0\n" >=cmd-param-changed,param="width",value="4294967295" >82^done >&"set height 0\n" >83^done >&"set detach-on-fork off\n" >=cmd-param-changed,param="detach-on-fork",value="off" >84^done >&"python sys.path.insert(1, '/usr/share/qtcreator/debugger/')\n" >85^done >&"python sys.path.append('/usr/bin/data-directory/python')\n" >86^done >&"python from gdbbridge import *\n" >87^done >&"python theDumper.loadDumpers({\"token\":88})\n" >~"result={token=\"88\",dumpers=[{type=\"QVariant (QVariantMap)\",formats=\"17\"},{type=\"QAtomicInt\"},{type=\"QBasicAtomicInt\"},{type=\"QAtomicPointer\"},{type=\"QByteArray\",formats=\"5, 6, 7, 8\"},{type=\"QArrayData\"},{type=\"QByteArrayData\"},{type=\"QBitArray\"},{type=\"QChar\"},{type=\"Qt__ItemDataRole\"},{type=\"QStandardItemData\"},{type=\"QStandardItem\"},{type=\"QDate\"},{type=\"QTime\"},{type=\"QTimeZone\"},{type=\"QDateTime\"},{type=\"QDir\"},{type=\"QFile\"},{type=\"QFileInfo\"},{type=\"QFixed\"},{type=\"QFiniteStack\",formats=\"16\"},{type=\"QFlags\"},{type=\"QHash\",formats=\"17\"},{type=\"QVariantHash\"},{type=\"QHashNode\",formats=\"17\"},{type=\"QHash__const_iterator\"},{type=\"QHash__iterator\"},{type=\"QHostAddress\"},{type=\"QIPv6Address\"},{type=\"QList\",formats=\"18, 19\"},{type=\"QVariantList\"},{type=\"QImage\",formats=\"2, 4\"},{type=\"QLinkedList\"},{type=\"QLocale\"},{type=\"QMapNode\"},{type=\"QMap\",formats=\"17\"},{type=\"QMultiMap\",formats=\"17\"},{type=\"QVariantMap\",formats=\"17\"},{type=\"QMetaMethod\"},{type=\"QMetaEnum\"},{type=\"QMetaProperty\"},{type=\"QMetaClassInfo\"},{type=\"QMetaObject\"},{type=\"QObjectPrivate__ConnectionList\"},{type=\"QPixmap\"},{type=\"QPoint\"},{type=\"QPointF\"},{type=\"QRect\"},{type=\"QRectF\"},{type=\"QRegExp\"},{type=\"QRegion\"},{type=\"QScopedPointer\"},{type=\"QSet\"},{type=\"QSharedData\"},{type=\"QSharedDataPointer\"},{type=\"QSize\"},{type=\"QSizeF\"},{type=\"QStack\",formats=\"16\"},{type=\"QPolygonF\"},{type=\"QPolygon\"},{type=\"QGraphicsPolygonItem\"},{type=\"QString\",editable=\"true\",formats=\"2, 4\"},{type=\"QStaticStringData\"},{type=\"QTypedArrayData\"},{type=\"QStringData\"},{type=\"QHashedString\"},{type=\"QQmlRefCount\"},{type=\"QStringRef\"},{type=\"QStringList\"},{type=\"QTemporaryFile\"},{type=\"QTextCodec\"},{type=\"QTextCursor\"},{type=\"QTextDocument\"},{type=\"QUrl\",formats=\"2, 4\"},{type=\"QUuid\"},{type=\"QVariant\"},{type=\"QVector\",editable=\"true\",formats=\"16\"},{type=\"QVarLengthArray\"},{type=\"QSharedPointer\"},{type=\"QWeakPointer\"},{type=\"QXmlAttributes__Attribute\"},{type=\"QXmlAttributes\"},{type=\"QXmlStreamStringRef\"},{type=\"QXmlStreamAttribute\"},{type=\"QV4__Heap__Base\"},{type=\"QV4__Heap__String\"},{type=\"QV4__Object\"},{type=\"QV4__FunctionObject\"},{type=\"QV4__CompilationUnit\"},{type=\"QV4__CallContext\"},{type=\"QV4__ScriptFunction\"},{type=\"QV4__SimpleScriptFunction\"},{type=\"QV4__ExecutionContext\"},{type=\"QQmlSourceLocation\"},{type=\"QV4__String\"},{type=\"QV4__Identifier\"},{type=\"QV4__PropertyHash\"},{type=\"QV4__InternalClass__Transition\"},{type=\"QV4__InternalClassTransition\"},{type=\"QV4__SharedInternalClassData\"},{type=\"QV4__IdentifierTable\"},{type=\"QV4_Object\"},{type=\"QV4__Value\"},{type=\"QV__PropertyHashData\"},{type=\"QV__PropertyHash\"},{type=\"QV4__Scoped\"},{type=\"QV4__ScopedString\"},{type=\"QJSValue\"},{type=\"QQmlBinding\"},{type=\"QTJSC__JSValue\"},{type=\"QScriptValue\"},{type=\"QQmlAccessorProperties__Properties\"},{type=\"QJsonPrivate__qle_bitfield\"},{type=\"QJsonPrivate__qle_signedbitfield\"},{type=\"QJsonPrivate__q_littleendian\"},{type=\"QJsonValue\"},{type=\"QJsonArray\"},{type=\"QJsonObject\"},{type=\"QSqlResultPrivate\"},{type=\"QSqlField\"},{type=\"QLazilyAllocated\"},{type=\"qfloat16\"},{type=\"std__array\",formats=\"16\"},{type=\"std____1__array\",formats=\"16\"},{type=\"std__complex\"},{type=\"std____1__complex\"},{type=\"std__deque\"},{type=\"std____1__deque\"},{type=\"std__deque__QNX\"},{type=\"std__deque__MSVC\"},{type=\"std____debug__deque\"},{type=\"std__list\"},{type=\"std__list__QNX\"},{type=\"std____debug__list\"},{type=\"std____cxx11__list\"},{type=\"std____1__list\"},{type=\"std__map\",formats=\"17\"},{type=\"std____debug__map\"},{type=\"std____debug__set\"},{type=\"std__multiset\"},{type=\"std____cxx1998__map\"},{type=\"std__multimap\",formats=\"17\"},{type=\"std___Rb_tree_iterator\"},{type=\"std___Rb_tree_const_iterator\"},{type=\"std__map__iterator\"},{type=\"__gnu_debug___Safe_iterator\"},{type=\"std__map__const_iterator\"},{type=\"std__set__iterator\"},{type=\"std__set__const_iterator\"},{type=\"std____cxx1998__set\"},{type=\"std___Tree_const_iterator\"},{type=\"std___Tree_iterator\"},{type=\"std__set\"},{type=\"std__set__QNX\"},{type=\"std____1__set\"},{type=\"std____1__multiset\"},{type=\"std____1__map\",formats=\"17\"},{type=\"std____1__multimap\",formats=\"17\"},{type=\"std____1__map__iterator\"},{type=\"std____1__map__const_iterator\"},{type=\"std____1__set__iterator\"},{type=\"std____1__set_const_iterator\"},{type=\"std__stack\"},{type=\"std____debug__stack\"},{type=\"std____1__stack\"},{type=\"std__string\",editable=\"true\",formats=\"5, 6, 7, 8\"},{type=\"std____1__string\"},{type=\"std____1__wstring\"},{type=\"std____weak_ptr\"},{type=\"std__weak_ptr\"},{type=\"std____1__weak_ptr\"},{type=\"std__shared_ptr\"},{type=\"std____1__shared_ptr\"},{type=\"std__unique_ptr\"},{type=\"std____1__unique_ptr\"},{type=\"std__pair\"},{type=\"std__unordered_map\",formats=\"17\"},{type=\"std____debug__unordered_map\",formats=\"17\"},{type=\"std__unordered_multimap\",formats=\"17\"},{type=\"std____debug__unordered_multimap\",formats=\"17\"},{type=\"std__unordered_set\"},{type=\"std____1__unordered_map\",formats=\"17\"},{type=\"std____1__unordered_set\"},{type=\"std____debug__unordered_set\"},{type=\"std__unordered_multiset\"},{type=\"std____debug__unordered_multiset\"},{type=\"std__valarray\",formats=\"16\"},{type=\"std____1__valarray\",formats=\"16\"},{type=\"std__vector\",editable=\"true\",formats=\"16\"},{type=\"std____1__vector\"},{type=\"std____debug__vector\",formats=\"16\"},{type=\"string\",editable=\"true\"},{type=\"std__wstring\",formats=\"2, 4\"},{type=\"std__basic_string\"},{type=\"std____cxx11__basic_string\"},{type=\"std____cxx11__string\",formats=\"5, 6, 7, 8\"},{type=\"std____cxx11__wstring\",formats=\"2, 4\"},{type=\"std____1__basic_string\"},{type=\"wstring\"},{type=\"std____1__once_flag\"},{type=\"std__once_flag\"},{type=\"__gnu_cxx__hash_set\"},{type=\"uint8_t\"},{type=\"int8_t\"},{type=\"__m128\"},{type=\"__m256\"},{type=\"__m512\"},{type=\"__m128d\"},{type=\"__m256d\"},{type=\"__m512d\"},{type=\"__m128i\"},{type=\"__m256i\"},{type=\"__m512i\"},{type=\"Eigen__Matrix\"},{type=\"NimStringDesc\"},{type=\"NimGenericSequence__\"},{type=\"TNimNode\"},{type=\"KDSoapValue1\"},{type=\"KDSoapValue\"},{type=\"WTF__String\"},{type=\"QtcDumperTest_FieldAccessByIndex\"},{type=\"QtcDumperTest_PointerArray\"},{type=\"QtcDumperTest_BufArray\"},{type=\"boost__bimaps__bimap\"},{type=\"boost__optional\"},{type=\"boost__shared_ptr\"},{type=\"boost__container__list\"},{type=\"boost__gregorian__date\"},{type=\"boost__posix_time__ptime\"},{type=\"boost__posix_time__time_duration\"},{type=\"boost__unordered__unordered_set\"},{type=\"boost__variant\"},{type=\"cv__Size_\"},{type=\"cv__Mat\",formats=\"4\"},{type=\"Core__Id\"},{type=\"Debugger__Internal__GdbMi\"},{type=\"Debugger__Internal__DisassemblerLine\"},{type=\"Debugger__Internal__WatchData\"},{type=\"Debugger__Internal__WatchItem\"},{type=\"Debugger__Internal__BreakpointModelId\"},{type=\"Debugger__Internal__ThreadId\"},{type=\"CPlusPlus__ByteArrayRef\"},{type=\"CPlusPlus__Identifier\"},{type=\"CPlusPlus__Symbol\"},{type=\"CPlusPlus__Class\"},{type=\"CPlusPlus__IntegerType\"},{type=\"CPlusPlus__FullySpecifiedType\"},{type=\"CPlusPlus__NamedType\"},{type=\"CPlusPlus__PointerType\"},{type=\"CPlusPlus__TemplateNameId\"},{type=\"CPlusPlus__QualifiedNameId\"},{type=\"CPlusPlus__Literal\"},{type=\"CPlusPlus__StringLiteral\"},{type=\"CPlusPlus__Internal__Value\"},{type=\"Utils__FileName\"},{type=\"Utils__ElfSection\"},{type=\"Utf8String\"},{type=\"CPlusPlus__Token\"},{type=\"CPlusPlus__Internal__PPToken\"},{type=\"ProString\"},{type=\"ProKey\"},{type=\"Core__GeneratedFile\"},{type=\"ProjectExplorer__Node\"},{type=\"ProjectExplorer__FolderNode\"},{type=\"ProjectExplorer__ProjectNode\"},{type=\"CMakeProjectManager__Internal__CMakeProjectNode\"},{type=\"QmakeProjectManager__QmakePriFileNode\"},{type=\"QmakeProjectManager__QmakeProFileNode\"},],python=\"30601\"}\n" >88^done dENGINE SUCCESSFULLY STARTED dNOTE: ENGINE SETUP OK dState changed from EngineSetupRequested(1) to EngineSetupOk(3) [master] dQUEUE: SETUP INFERIOR dState changed from EngineSetupOk(3) to InferiorSetupRequested(4) [master] dQUEUE: SETUP INFERIOR >89^done dCALL: SETUP INFERIOR <90unset environment CASROOT <91unset environment CSF_EXCEPTION_PROMPT <92unset environment CSF_GraphicShr <93unset environment CSF_IGESDefaults <94unset environment CSF_LANGUAGE <95unset environment CSF_MDTVTexturesDirectory <96unset environment CSF_PluginDefaults <97unset environment CSF_SHMessage <98unset environment CSF_STEPDefaults <99unset environment CSF_StandardDefaults <100unset environment CSF_StandardLiteDefaults <101unset environment CSF_UnitsDefinition <102unset environment CSF_UnitsLexicon <103unset environment CSF_XCAFDefaults <104unset environment CSF_XSMessage <105unset environment CSF_XmlOcafResource <106unset environment DBUS_SESSION_BUS_ADDRESS <107unset environment DESKTOP_SESSION <108unset environment DISPLAY <109unset environment GS_LIB <110unset environment GTK_MODULES <111unset environment HG <112unset environment HOME <113unset environment KDE_FULL_SESSION <114unset environment KDE_SESSION_UID <115unset environment KDE_SESSION_VERSION <116unset environment LANG <117unset environment LANGUAGE <118unset environment LARCH_PATH <119unset environment LCLIMPORTDIR <120unset environment LD_LIBRARY_PATH <121unset environment LOGNAME <122unset environment MAIL <123unset environment MMGT_CLEAR <124unset environment MOZ_PLUGIN_PATH <125unset environment PATH <126unset environment PWD <127unset environment QSG_RENDER_LOOP <128unset environment QT_AUTO_SCREEN_SCALE_FACTOR <129unset environment QT_LOGGING_TO_CONSOLE <130unset environment SESSION_MANAGER <131unset environment SHELL <132unset environment SHLVL <133unset environment USER <134unset environment XAUTHORITY <135unset environment XCURSOR_THEME <136unset environment XDG_CURRENT_DESKTOP <137unset environment XDG_DATA_DIRS <138unset environment XDG_RUNTIME_DIR <139unset environment XDG_SEAT <140unset environment XDG_SEAT_PATH <141unset environment XDG_SESSION_CLASS <142unset environment XDG_SESSION_DESKTOP <143unset environment XDG_SESSION_ID <144unset environment XDG_SESSION_PATH <145unset environment XDG_SESSION_TYPE <146unset environment XDG_VTNR <147unset environment _ <148-file-exec-and-symbols "/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.elf" >&"unset environment CASROOT\n" >90^done >&"unset environment CSF_EXCEPTION_PROMPT\n" >91^done >&"unset environment CSF_GraphicShr\n" >92^done >&"unset environment CSF_IGESDefaults\n" >93^done >&"unset environment CSF_LANGUAGE\n" >94^done >&"unset environment CSF_MDTVTexturesDirectory\n" >95^done >&"unset environment CSF_PluginDefaults\n" >96^done >&"unset environment CSF_SHMessage\n" >97^done >&"unset environment CSF_STEPDefaults\n" >98^done >&"unset environment CSF_StandardDefaults\n" >99^done >&"unset environment CSF_StandardLiteDefaults\n" >100^done >&"unset environment CSF_UnitsDefinition\n" >101^done >&"unset environment CSF_UnitsLexicon\n" >102^done >&"unset environment CSF_XCAFDefaults\n" >103^done >&"unset environment CSF_XSMessage\n" >104^done >&"unset environment CSF_XmlOcafResource\n" >105^done >&"unset environment DBUS_SESSION_BUS_ADDRESS\n" >106^done >&"unset environment DESKTOP_SESSION\n" >107^done >&"unset environment DISPLAY\n" >108^done >&"unset environment GS_LIB\n" >109^done >&"unset environment GTK_MODULES\n" >110^done >&"unset environment HG\n" >111^done >&"unset environment HOME\n" >112^done >&"unset environment KDE_FULL_SESSION\n" >113^done >&"unset environment KDE_SESSION_UID\n" >114^done >&"unset environment KDE_SESSION_VERSION\n" >115^done >&"unset environment LANG\n" >116^done >&"unset environment LANGUAGE\n" >117^done >&"unset environment LARCH_PATH\n" >118^done >&"unset environment LCLIMPORTDIR\n" >119^done >&"unset environment LD_LIBRARY_PATH\n" >120^done >&"unset environment LOGNAME\n" >121^done >&"unset environment MAIL\n" >122^done >&"unset environment MMGT_CLEAR\n" >123^done >&"unset environment MOZ_PLUGIN_PATH\n" >124^done >&"unset environment PATH\n" >125^done >&"unset environment PWD\n" >126^done >&"unset environment QSG_RENDER_LOOP\n" >127^done >&"unset environment QT_AUTO_SCREEN_SCALE_FACTOR\n" >128^done >&"unset environment QT_LOGGING_TO_CONSOLE\n" >129^done >&"unset environment SESSION_MANAGER\n" >130^done >&"unset environment SHELL\n" >131^done >&"unset environment SHLVL\n" >132^done >&"unset environment USER\n" >133^done >&"unset environment XAUTHORITY\n" >134^done >&"unset environment XCURSOR_THEME\n" >135^done >&"unset environment XDG_CURRENT_DESKTOP\n" >136^done >&"unset environment XDG_DATA_DIRS\n" >137^done >&"unset environment XDG_RUNTIME_DIR\n" >138^done >&"unset environment XDG_SEAT\n" >139^done >&"unset environment XDG_SEAT_PATH\n" >140^done >&"unset environment XDG_SESSION_CLASS\n" >141^done >&"unset environment XDG_SESSION_DESKTOP\n" >142^done >&"unset environment XDG_SESSION_ID\n" >143^done >&"unset environment XDG_SESSION_PATH\n" >144^done >&"unset environment XDG_SESSION_TYPE\n" >145^done >&"unset environment XDG_VTNR\n" >146^done >&"unset environment _\n" >147^done >148^done <149target remote tcp:localhost:1234 >&"target remote tcp:localhost:1234\n" >~"Remote debugging using tcp:localhost:1234\n" >=thread-group-started,id="i1",pid="42000" sThread-Gruppe i1 erzeugt dPID 42000 gemeldet >=thread-created,id="1",group-id="i1" sThread 1 erzeugt >~"0x00000000 in __vectors ()\n" >*stopped,frame={addr="0x00000000",func="__vectors",args=[]},thread-id="1",stopped-threads="all" eERROR: UNEXPECTED STATE: InferiorSetupRequested WANTED: InferiorStopOk IN ../../../../qt-creator-opensource-src-4.3.0/src/plugins/debugger/gdb/gdbengine.cpp:1426 eERROR: UNEXPECTED STATE: InferiorSetupRequested WANTED: InferiorStopOk IN ../../../../qt-creator-opensource-src-4.3.0/src/plugins/debugger/gdb/gdbengine.cpp:1438 <150importPlainDumpers off eERROR: UNEXPECTED STATE: InferiorSetupRequested WANTED: InferiorStopOk IN ../../../../qt-creator-opensource-src-4.3.0/src/plugins/debugger/gdb/gdbengine.cpp:1510 sAngehalten. >149^done dINFERIOR STARTED sDebugger an angehaltene Anwendung angehängt sSetze Haltepunkte... dSetze Haltepunkte... dATTEMPT BREAKPOINT SYNCHRONIZATION dTAKING OWNERSHIP OF BREAKPOINT 1 IN STATE 0 dTAKING OWNERSHIP OF BREAKPOINT 2 IN STATE 0 dRUNNING NEEDS-STOP COMMAND -break-insert -f "\"avr0000.cc\":25" dUNSAFE STATE FOR QUEUED COMMAND. EXECUTING IMMEDIATELY <151-break-insert -f "\"avr0000.cc\":25" dRUNNING NEEDS-STOP COMMAND -break-insert -f "\"ppc5000.cc\":25" dUNSAFE STATE FOR QUEUED COMMAND. EXECUTING IMMEDIATELY <152-break-insert -f "\"ppc5000.cc\":25" dBREAKPOINTS ARE NOT FULLY SYNCHRONIZED <153-thread-info >&"importPlainDumpers off\n" >~"1 printer disabled\n" >~"0 of 1 printers enabled\n" >~"None\n" >150^done >151^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x00000090",func="main()",file="/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.cc",fullname="/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.cc",line="25",thread-groups=["i1"],times="0",original-location="avr0000.cc:25"} >&"No source file named ppc5000.cc.\n" >152^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="",pending="\"ppc5000.cc\":25",times="0",original-location="\"ppc5000.cc\":25"} dATTEMPT BREAKPOINT SYNCHRONIZATION dBREAKPOINTS ARE SYNCHRONIZED >153^done,threads=[{id="1",target-id="Thread
",frame={level="0",addr="0x00000000",func="__vectors",args=[]},state="stopped"}],current-thread-id="1" <154python theDumper.fetchStack({"limit":20,"nativemixed":0,"token":154}) >&"python theDumper.fetchStack({\"limit\":20,\"nativemixed\":0,\"token\":154})\n" >~"result={token=\"0\",stack={frames=[frame={level=\"0\",address=\"0x0\",function=\"__vectors\",file=\"\",line=\"0\",module=\"\",language=\"c\"}].report}}\n" >154^done dALL COMMANDS DONE; INVOKING CALLBACK dNOTE: INFERIOR SETUP OK dState changed from InferiorSetupRequested(4) to InferiorSetupOk(6) [master] dState changed from InferiorSetupOk(6) to EngineRunRequested(7) [master] dQUEUE: RUN ENGINE dCALL: RUN ENGINE dNOTE: ENGINE RUN AND INFERIOR STOP OK sAngehalten. dState changed from EngineRunRequested(7) to InferiorStopOk(14) [master] dNOTE: INFERIOR RUN REQUESTED sAusführung angefordert... dState changed from InferiorStopOk(14) to InferiorRunRequested(10) [master] sFortsetzung angefordert... <155-exec-continue >155^running dNOTE: INFERIOR RUN OK sLäuft. dState changed from InferiorRunRequested(10) to InferiorRunOk(11) [master] >*running,thread-id="all" dNOTE: INFERIOR STILL RUNNING IN STATE InferiorRunOk. >~"Note: automatically using hardware breakpoints for read-only addresses.\n" >=breakpoint-modified,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x00000090",func="main()",file="/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.cc",fullname="/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.cc",line="25",thread-groups=["i1"],times="1",original-location="avr0000.cc:25"} >~"\n" >~"Breakpoint 1, main () at /home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.cc:25\n" >~"25\t ++x; \n" >*stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame={addr="0x00000090",func="main",args=[],file="/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.cc",fullname="/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.cc",line="25"},thread-id="1",stopped-threads="all" dNOTE: INFERIOR SPONTANEOUS STOP sAngehalten. dState changed from InferiorRunOk(11) to InferiorStopOk(14) [master] sAn Haltepunkt 1 (1) im Thread 1 angehalten. >&"p 0\n" >~"$1 = 0" >~"\n" >^done <156-thread-info >156^done,threads=[{id="1",target-id="Thread
",frame={level="0",addr="0x00000090",func="main",args=[],file="/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.cc",fullname="/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.cc",line="25"},state="stopped"}],current-thread-id="1" <157python theDumper.fetchStack({"limit":20,"nativemixed":0,"token":157}) >&"python theDumper.fetchStack({\"limit\":20,\"nativemixed\":0,\"token\":157})\n" >~"result={token=\"0\",stack={frames=[frame={level=\"0\",address=\"0x90\",function=\"main\",file=\"/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.cc\",line=\"25\",module=\"/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/ppc/src/ppc50/avr/avr0000.elf\",language=\"c\"}].report}}\n" >157^done <158-stack-select-frame 0 <159python theDumper.fetchVariables({"autoderef":1,"context":"","displaystringlimit":"100","dyntype":1,"expanded":["local","return","watch","inspect"],"fancy":1,"formats":{},"nativemixed":0,"partialvar":"","passexceptions":0,"qobjectnames":1,"resultvarname":"","stringcutoff":"10000","token":159,"typeformats":{},"watchers":[{"exp":"78","iname":"watch.0"}]}) <160maintenance print raw-registers <161-data-list-register-values r >158^done >&"python theDumper.fetchVariables({\"autoderef\":1,\"context\":\"\",\"displaystringlimit\":\"100\",\"dyntype\":1,\"expanded\":[\"local\",\"return\",\"watch\",\"inspect\"],\"fancy\":1,\"formats\":{},\"nativemixed\":0,\"partialvar\":\"\",\"passexceptions\":0,\"qobjectnames\":1,\"resultvarname\":\"\",\"stringcutoff\":\"10000\",\"token\":159,\"typeformats\":{},\"watchers\":[{\"exp\":\"78\",\"iname\":\"watch.0\"}]})\n" >~"result={token=\"0\",data=[{iname=\"watch.0\",wname=\"78\",numchild=\"0\",type=\"uint8_t\",value=\"0\",},],typeinfo=[],partial=\"0\",counts={},timimgs=[]}\n" >159^done sAlle Daten erhalten >&"maintenance print raw-registers\n" >~" Name Nr Rel Offset Size Type Raw value\n" >~" r0 0 0 0 1 uint8_t \n" >~" r1 1 1 1 1 uint8_t \n" >~" r2 2 2 2 1 uint8_t \n" >~" r3 3 3 3 1 uint8_t \n" >~" r4 4 4 4 1 uint8_t \n" >~" r5 5 5 5 1 uint8_t \n" >~" r6 6 6 6 1 uint8_t \n" >~" r7 7 7 7 1 uint8_t \n" >~" r8 8 8 8 1 uint8_t \n" >~" r9 9 9 9 1 uint8_t \n" >~" r10 10 10 10 1 uint8_t \n" >~" r11 11 11 11 1 uint8_t \n" >~" r12 12 12 12 1 uint8_t \n" >~" r13 13 13 13 1 uint8_t \n" >~" r14 14 14 14 1 uint8_t \n" >~" r15 15 15 15 1 uint8_t \n" >~" r16 16 16 16 1 uint8_t \n" >~" r17 17 17 17 1 uint8_t \n" >~" r18 18 18 18 1 uint8_t \n" >~" r19 19 19 19 1 uint8_t \n" >~" r20 20 20 20 1 uint8_t \n" >~" r21 21 21 21 1 uint8_t \n" >~" r22 22 22 22 1 uint8_t \n" >~" r23 23 23 23 1 uint8_t \n" >~" r24 24 24 24 1 uint8_t \n" >~" r25 25 25 25 1 uint8_t \n" >~" r26 26 26 26 1 uint8_t \n" >~" r27 27 27 27 1 uint8_t \n" >~" r28 28 28 28 1 uint8_t \n" >~" r29 29 29 29 1 uint8_t \n" >~" r30 30 30 30 1 uint8_t \n" >~" r31 31 31 31 1 uint8_t \n" >~" SREG 32 32 32 1 uint8_t 0x00\n" >~" SP 33 33 33 2 *1 0x08fd\n" >~" PC2 34 34 35 4 uint32_t 0x00000090\n" >~" pc 35 0 39 4 *1 \n" >~"*1: Register type's name NULL.\n" >160^done >161^done,register-values=[{number="0",value="0x00"},{number="1",value="0x00"},{number="2",value="0x00"},{number="3",value="0x00"},{number="4",value="0x00"},{number="5",value="0x00"},{number="6",value="0x00"},{number="7",value="0x00"},{number="8",value="0x00"},{number="9",value="0x00"},{number="10",value="0x00"},{number="11",value="0x00"},{number="12",value="0x00"},{number="13",value="0x00"},{number="14",value="0x00"},{number="15",value="0x00"},{number="16",value="0x00"},{number="17",value="0x00"},{number="18",value="0x01"},{number="19",value="0x00"},{number="20",value="0x00"},{number="21",value="0x00"},{number="22",value="0x00"},{number="23",value="0x00"},{number="24",value="0x00"},{number="25",value="0x00"},{number="26",value="0x01"},{number="27",value="0x01"},{number="28",value="0xff"},{number="29",value="0x08"},{number="30",value="0x00"},{number="31",value="0x00"},{number="32",value="0x02"},{number="33",value="0x000008fd"},{number="34",value="0x00000090"},{number="35",value="0x00000048"}] <162set disassembly-flavor att <163-interpreter-exec console "disassemble /rm 0x90" >&"set disassembly-flavor att\n" >&"No symbol \"disassembly\" in current context.\n" >162^error,msg="No symbol \"disassembly\" in current context." >&"No function contains specified address.\n" >163^error,msg="No function contains specified address." <164-interpreter-exec console "disassemble /rm 0x7c,0xf4" >~"Dump of assembler code from 0x80007c to 0x8000f4:\n" >~" 0x0080007c:\t00 00\tnop\n" >~" 0x0080007e:\t00 00\tnop\n" >~" 0x00800080:\t00 00\tnop\n" >~" 0x00800082:\t00 00\tnop\n" >~" 0x00800084:\t00 00\tnop\n" >~" 0x00800086:\t00 00\tnop\n" >~" 0x00800088:\t00 00\tnop\n" >~" 0x0080008a:\t00 00\tnop\n" >~" 0x0080008c:\t00 00\tnop\n" >~" 0x0080008e:\t00 00\tnop\n" >~" 0x00800090:\t00 00\tnop\n" >~" 0x00800092:\t00 00\tnop\n" >~" 0x00800094:\t00 00\tnop\n" >~" 0x00800096:\t00 00\tnop\n" >~" 0x00800098:\t00 00\tnop\n" >~" 0x0080009a:\t00 00\tnop\n" >~" 0x0080009c:\t00 00\tnop\n" >~" 0x0080009e:\t00 00\tnop\n" >~" 0x008000a0:\t00 00\tnop\n" >~" 0x008000a2:\t00 00\tnop\n" >~" 0x008000a4:\t00 00\tnop\n" >~" 0x008000a6:\t00 00\tnop\n" >~" 0x008000a8:\t00 00\tnop\n" >~" 0x008000aa:\t00 00\tnop\n" >~" 0x008000ac:\t00 00\tnop\n" >~" 0x008000ae:\t00 00\tnop\n" >~" 0x008000b0:\t00 00\tnop\n" >~" 0x008000b2:\t00 00\tnop\n" >~" 0x008000b4:\t00 00\tnop\n" >~" 0x008000b6:\t00 00\tnop\n" >~" 0x008000b8:\t00 f8\tbld\tr0, 0\n" >~" 0x008000ba:\t00 00\tnop\n" >~" 0x008000bc:\t00 00\tnop\n" >~" 0x008000be:\t00 00\tnop\n" >~" 0x008000c0:\t20 08\tsbc\tr2, r0\n" >~" 0x008000c2:\t06 00\t.word\t0x0006\t; ????\n" >~" 0x008000c4:\t00 00\tnop\n" >~" 0x008000c6:\t00 00\tnop\n" >~" 0x008000c8:\t00 00\tnop\n" >~" 0x008000ca:\t00 00\tnop\n" >~" 0x008000cc:\t00 00\tnop\n" >~" 0x008000ce:\t00 00\tnop\n" >~" 0x008000d0:\t00 00\tnop\n" >~" 0x008000d2:\t00 00\tnop\n" >~" 0x008000d4:\t00 00\tnop\n" >~" 0x008000d6:\t00 00\tnop\n" >~" 0x008000d8:\t00 00\tnop\n" >~" 0x008000da:\t00 00\tnop\n" >~" 0x008000dc:\t00 00\tnop\n" >~" 0x008000de:\t00 00\tnop\n" >~" 0x008000e0:\t00 00\tnop\n" >~" 0x008000e2:\t00 00\tnop\n" >~" 0x008000e4:\t00 00\tnop\n" >~" 0x008000e6:\t00 00\tnop\n" >~" 0x008000e8:\t00 00\tnop\n" >~" 0x008000ea:\t00 00\tnop\n" >~" 0x008000ec:\t00 00\tnop\n" >~" 0x008000ee:\t00 00\tnop\n" >~" 0x008000f0:\t00 00\tnop\n" >~" 0x008000f2:\t00 00\tnop\n" >~"End of assembler dump.\n" >164^done <165disassemble /r 0x7c,0xf4 >&"disassemble /r 0x7c,0xf4\n" >~"Dump of assembler code from 0x80007c to 0x8000f4:\n" >~" 0x0080007c:\t00 00\tnop\n" >~" 0x0080007e:\t00 00\tnop\n" >~" 0x00800080:\t00 00\tnop\n" >~" 0x00800082:\t00 00\tnop\n" >~" 0x00800084:\t00 00\tnop\n" >~" 0x00800086:\t00 00\tnop\n" >~" 0x00800088:\t00 00\tnop\n" >~" 0x0080008a:\t00 00\tnop\n" >~" 0x0080008c:\t00 00\tnop\n" >~" 0x0080008e:\t00 00\tnop\n" >~" 0x00800090:\t00 00\tnop\n" >~" 0x00800092:\t00 00\tnop\n" >~" 0x00800094:\t00 00\tnop\n" >~" 0x00800096:\t00 00\tnop\n" >~" 0x00800098:\t00 00\tnop\n" >~" 0x0080009a:\t00 00\tnop\n" >~" 0x0080009c:\t00 00\tnop\n" >~" 0x0080009e:\t00 00\tnop\n" >~" 0x008000a0:\t00 00\tnop\n" >~" 0x008000a2:\t00 00\tnop\n" >~" 0x008000a4:\t00 00\tnop\n" >~" 0x008000a6:\t00 00\tnop\n" >~" 0x008000a8:\t00 00\tnop\n" >~" 0x008000aa:\t00 00\tnop\n" >~" 0x008000ac:\t00 00\tnop\n" >~" 0x008000ae:\t00 00\tnop\n" >~" 0x008000b0:\t00 00\tnop\n" >~" 0x008000b2:\t00 00\tnop\n" >~" 0x008000b4:\t00 00\tnop\n" >~" 0x008000b6:\t00 00\tnop\n" >~" 0x008000b8:\t00 f8\tbld\tr0, 0\n" >~" 0x008000ba:\t00 00\tnop\n" >~" 0x008000bc:\t00 00\tnop\n" >~" 0x008000be:\t00 00\tnop\n" >~" 0x008000c0:\t20 08\tsbc\tr2, r0\n" >~" 0x008000c2:\t06 00\t.word\t0x0006\t; ????\n" >~" 0x008000c4:\t00 00\tnop\n" >~" 0x008000c6:\t00 00\tnop\n" >~" 0x008000c8:\t00 00\tnop\n" >~" 0x008000ca:\t00 00\tnop\n" >~" 0x008000cc:\t00 00\tnop\n" >~" 0x008000ce:\t00 00\tnop\n" >~" 0x008000d0:\t00 00\tnop\n" >~" 0x008000d2:\t00 00\tnop\n" >~" 0x008000d4:\t00 00\tnop\n" >~" 0x008000d6:\t00 00\tnop\n" >~" 0x008000d8:\t00 00\tnop\n" >~" 0x008000da:\t00 00\tnop\n" >~" 0x008000dc:\t00 00\tnop\n" >~" 0x008000de:\t00 00\tnop\n" >~" 0x008000e0:\t00 00\tnop\n" >~" 0x008000e2:\t00 00\tnop\n" >~" 0x008000e4:\t00 00\tnop\n" >~" 0x008000e6:\t00 00\tnop\n" >~" 0x008000e8:\t00 00\tnop\n" >~" 0x008000ea:\t00 00\tnop\n" >~" 0x008000ec:\t00 00\tnop\n" >~" 0x008000ee:\t00 00\tnop\n" >~" 0x008000f0:\t00 00\tnop\n" >~" 0x008000f2:\t00 00\tnop\n" >~"End of assembler dump.\n" >165^done sFehler beim Disassemblieren: Maybe its a user error? -- Wilhelm From gotschmarcel+qtcreator at gmail.com Wed May 31 11:30:10 2017 From: gotschmarcel+qtcreator at gmail.com (Marcel Gotsch) Date: Wed, 31 May 2017 11:30:10 +0200 Subject: [Qt-creator] How to depend on Qt-Creator target Message-ID: Hello, I’m building a plugin for the Qt Creator and cannot figure out how to get qmake to depend on the Qt Creator target. I want that the Qt Creator target is automatically build before the plugin is build. The qtcreator.pri seems to be included by the qtcreatorplugin.pri, so the target should be available. Another question that comes up is how the plugin can be distributed to users. I have some people that would like to use the plugin, but currently they would have to build the plugin themselves. Also, are they required to use same Qt Creator source code version as their installed Qt Creator has? Any help is really appreciated :) Best, Marcel From Eike.Ziller at qt.io Wed May 31 12:14:13 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Wed, 31 May 2017 10:14:13 +0000 Subject: [Qt-creator] How to depend on Qt-Creator target In-Reply-To: References: Message-ID: > On May 31, 2017, at 11:30 AM, Marcel Gotsch wrote: > > Hello, > > I’m building a plugin for the Qt Creator and cannot figure out how to get qmake to depend on the Qt Creator target. > I want that the Qt Creator target is automatically build before the plugin is build. The qtcreator.pri seems to be included > by the qtcreatorplugin.pri, so the target should be available. Either you mark that dependency solely in builds done from Qt Creator (Projects mode, “Dependencies” section for the plugin project), or, the usual IDE agnostic way to do that with qmake is to create a separate subdirs project which has Qt Creator and the plugin as a subdir. > Another question that comes up is how the plugin can be distributed to users. I have some people that would like to use > the plugin, but currently they would have to build the plugin themselves. Also, are they required to use same Qt Creator > source code version as their installed Qt Creator has? If you (or someone else) wants to build the plugin for use in a binary install from the Qt Project of Qt Creator, you can use the qtcreator_dev.7zip that we provide on our download page (e.g. http://download.qt.io/official_releases/qtcreator/4.3/4.3.0/installer_source/windows_vs2015_64/) as the “IDE_SOURCE_TREE”, and the location of the binary install of Qt Creator as the “IDE_BUILD_TREE”. If you do not want to use the _dev package, you/they need to use the exact same Qt Creator sources as the install, and at least on Windows it is required to build that too (to get the required .lib files). In any case you should use the same Qt version, and a compatible C++ compiler version, as shown in the About Qt Creator dialog, and do a release build. If you want to create distributable binaries of your plugin, you can additionally set IDE_OUTPUT_PATH to some directory, do a build, and zip the contents in that path up. It should then be possibly to unzip that into the installed Qt Creator. Br, Eike > Any help is really appreciated :) > > Best, > Marcel > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From broothy at gmail.com Thu May 25 08:49:33 2017 From: broothy at gmail.com (=?UTF-8?B?w4Fkw6FtIEJhbMOhenM=?=) Date: Thu, 25 May 2017 06:49:33 -0000 Subject: [Qt-creator] Qt Creator predefined macro file In-Reply-To: References: Message-ID: I have tried it out but it had no effect on code completion. As a workaround we included the macro file temporarily in one of our basic components. If I comment out that include the code completion fails again with the suggested solution too. It is just a temporary workaround, we would like to solve the problem properly (as our colleagues did it in Eclipse with setting the preprocessor macros file). 2017-05-24 19:49 GMT+02:00 Orgad Shaneh : > Try this: > > PRECOMPILED_HEADER = your_header.h > CONFIG -= precompile_header # prevent actually passing it to the compiler > (it is configured by default on Windows) > > בתאריך 24 במאי 2017 18:32,‏ "Ádám Balázs" כתב: > >> Hi, >> >> Our project has a predefined macro file that is given to the compiler >> (GCC/Clang) with the -imacros flag. It contains the platform specific >> macros so it is a complicated and long file. Can I specify a predefined >> macro file in Qt Creator because without it the code completion fails? I >> know that I can specify my macros in the DEFINES section of the .pro file >> but we have them in a standalone file. It is not possible to move them into >> the .pro file because other colleagues use Eclipse. Adding -imacros in >> QMAKE_CXXFLAGS has no effect on code completion. >> In Eclipse you can set it on this screen: http://imgur.com/a/AVFMO >> Is there a similar setting in Qt Creator? >> >> Adam >> >> _______________________________________________ >> Qt-creator mailing list >> Qt-creator at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/qt-creator >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From guenter at vikingsoft.eu Tue May 30 08:56:32 2017 From: guenter at vikingsoft.eu (Guenter Schwann) Date: Tue, 30 May 2017 06:56:32 -0000 Subject: [Qt-creator] QtC 4.3 cmake-servermode feature - how to disable that? In-Reply-To: References: <530a3231-681c-92f4-6683-3c85db03e35d@yandex.ru> Message-ID: <3018186.jPIQVuUVhY@w541> On Montag, 29. Mai 2017 11:02:48 CEST Tobias Hunger wrote: > That is how cmake sees your project:-) But it's not what (most of) the developers (want to) see. I mean the mental model of the developer is now quite different than the cmake model. As I'd say most developers see their project the same as it's in the file system. But I can see some value in the new view. Therefore I'd suggest to improve the file system view. Currently it lists a single directory. But when it would show a tree (expandable/collapsible) that view would fit many cases/developers very well. -- Viking Software http://www.vikingsoft.eu From wilhelm.meier at hs-kl.de Tue May 30 12:22:43 2017 From: wilhelm.meier at hs-kl.de (Wilhelm Meier) Date: Tue, 30 May 2017 10:22:43 -0000 Subject: [Qt-creator] Using QtC together with simavr Message-ID: <1ac02c21-e872-6004-6a56-c00a75c02aff@hs-kl.de> Hi all, I would like to use QtC together with simavr which provides a gdb remote interface. I managed to configure a bare metal device, that connects to a running simavr process on localhost:1234. Debugging works. But: I have to start/stop the simavr manually before/after debugging with QtC. Is there a way to configure a "pre-debug" step (like some sort of deployment) prior to start the debugging in QtC? For bare metal targets there is no chance to actvate a deployment step in QtC. I'm using QtC 4.3.0 Thanks, Wilhelm From gotschmarcel at gmail.com Wed May 31 11:23:22 2017 From: gotschmarcel at gmail.com (Marcel Gotsch) Date: Wed, 31 May 2017 09:23:22 -0000 Subject: [Qt-creator] How to depend on Qt Creator target Message-ID: <2DEF7961-E57B-4D1E-AAAA-21261423274A@gmail.com> Hello, I’m building a plugin for the Qt Creator and cannot figure out how to get qmake to depend on the Qt Creator target. I want that the Qt Creator target is automatically build before the plugin is build. The qtcreator.pri seems to be included by the qtcreatorplugin.pri, so the target should be available. Another question that comes up is how the plugin can be distributed to users. I have some people that would like to use the plugin, but currently they would have to build the plugin themselves. Also, are they required to use same Qt Creator source code version as their installed Qt Creator has? Any help is really appreciated :) Best, Marcel