Re: [Qt-creator] Hiding windows in debug mode
On Mon, Oct 18, 2010 at 12:27 PM, anshul mehta wrote: > One thing you can try is that make sure the debugging session is stopped > when you remove(uncheck) from Window->views->debugger > After then restart. > I tested it again and now the debugger view does not open automatically (it is unchecked in the menu Window->views->debugger). I'm confused but happy. I'm using QT Creator 2.0.1. PS: I switched some weeks ago from Wind River Sniff+/Visual Studio to QT Creator. Thank you for such a wonderful tool. ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Hiding windows in debug mode
One thing you can try is that make sure the debugging session is stopped when you remove(uncheck) from Window->views->debugger After then restart. On Mon, Oct 18, 2010 at 3:51 PM, Alfred Gebert wrote: > On Mon, Oct 18, 2010 at 11:00 AM, Eike Ziller > wrote: > > > > On Oct 18, 2010, at 10:54 AM, ext Sergey wrote: > > > >> Does any one know how to hide this window (highlighted with red on > screenshoot) ? It started to appear when I launch application in the debug > mode. > > I have the same question. > > > > > Window->Views->Debugger Log, though it should not appear "just so". > > > > I can remove the view with this menu entry but the next time I start > the debugger the debugger log view will open again. > > Alfred > ___ > Qt-creator mailing list > Qt-creator@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-creator > ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Hiding windows in debug mode
On Mon, Oct 18, 2010 at 11:00 AM, Eike Ziller wrote: > > On Oct 18, 2010, at 10:54 AM, ext Sergey wrote: > >> Does any one know how to hide this window (highlighted with red on >> screenshoot) ? It started to appear when I launch application in the debug >> mode. I have the same question. > > Window->Views->Debugger Log, though it should not appear "just so". > I can remove the view with this menu entry but the next time I start the debugger the debugger log view will open again. Alfred ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Hiding windows in debug mode
On Oct 18, 2010, at 10:54 AM, ext Sergey wrote: > Does any one know how to hide this window (highlighted with red on > screenshoot) ? It started to appear when I launch application in the debug > mode. Window->Views->Debugger Log, though it should not appear "just so". Br, Eike ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] [PATCH] remotegdbserveradapter: pass parameters to the server start script
* this allows to have a generic script which can upload and launch
the program to debug on the target.
* example of a such script :
USER=root
{ ssh $u...@$1 killall -9 gdbserver &> /dev/null ; ssh $u...@$1 killall -9 $4
&> /dev/null ; sleep 1; scp $3/$4 $u...@$1:/tmp/ &> /dev/null ; }
ssh $u...@$1 gdbserver --wrapper env
QWS_MOUSE_PROTO=tslib:/dev/input/touchscreen0 -- :$2 /tmp/$4 -qws &
exit 0
* Parameters passed to the script are :
$1 : IP of the target
$2 : port for gdbserver
$3 : path to the application's binary
$4 : application's binary name
$5 : path to gdb on the host (can give access to the toolchain)
$6 : name of gdb on the host (can give access to the prefix of the tools,
in order, for example to strip the binary in the script before
send it to the target.
* tested using QT-Creator, a toolchain generated with OpenEmbedded's
meta-toolchain-qte recipe and and ARMv5 target.
Signed-off-by: Eric Bénard
---
.../debugger/gdb/remotegdbserveradapter.cpp|8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/src/plugins/debugger/gdb/remotegdbserveradapter.cpp
b/src/plugins/debugger/gdb/remotegdbserveradapter.cpp
index 86fa9ed..ffadec9 100644
--- a/src/plugins/debugger/gdb/remotegdbserveradapter.cpp
+++ b/src/plugins/debugger/gdb/remotegdbserveradapter.cpp
@@ -96,7 +96,13 @@ void RemoteGdbServerAdapter::startAdapter()
showMessage(_("No server start script given. "), StatusBar);
emit requestSetup();
} else {
-m_uploadProc.start(_("/bin/sh ") +
startParameters().serverStartScript);
+m_uploadProc.start(_("/bin/sh ") + startParameters().serverStartScript
+
+ _(" ") + startParameters().remoteChannel.split(':').first() +
+ _(" ") + startParameters().remoteChannel.split(':').last() +
+ _(" ") + QFileInfo(startParameters().executable).absolutePath() +
+ _(" ") + QFileInfo(startParameters().executable).baseName() +
+ _(" ") +
QFileInfo(startParameters().debuggerCommand).absolutePath() +
+ _(" ") + QFileInfo(startParameters().debuggerCommand).baseName());
m_uploadProc.waitForStarted();
}
}
--
1.7.0.4
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Install support files together with plugin
On Mon, Oct 18, 2010 at 9:31 AM, Eike Ziller wrote:
> But, if you consider to provide your plugin cross-platform, you should notice
> that resources are at a different place on Mac builds.
> You should definitely use $$IDE_DATA_PATH/myplugin/scripts
> and in you plugin sources Core::ICore::instance()->resourcePath() +
> QLatin1String("/myplugin/scripts")
>
Thanks for the tip.
>
> INSTALLS creates an additional make target "make install". If you don't call
> "make install" the files will not be copied. If you want to actually copy
> files during the "make" step, you'll unfortunately need to do some fancy
> stuff, similar to share/qtcreator/static.pro
> /me wonders if we couldn't provide most of the stuff for this task as
> functions in qtcreator.pri ?
>
I was, and still am, confused by how the plugin gets build and installed.
When I build the plugin from within Qt Creator, it gets installed
automatically, I never have to use make install.
Running make install from the build dir works, but results in an
error. It wants to create a directory called "/lib/qtcreator".
Thanks for the reply. I have an answer to my question. Just run make
install in the build dir regardless of building the plugin in Qt
Creator.
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Debugging/ptrace problems in Ubuntu 10.10
On Oct 17, 2010, at 9:21 PM, ext Andre Poenitz wrote: > On Sat, Oct 16, 2010 at 07:13:11PM +0300, Juha Ruotsalainen wrote: >> Hi there! >> >> Can someone more knowledgeable than I give a good answer how to proceed with >> this problem: >> I'm running Ubuntu 10.10 and Qt Creator cannot debug there due to 10.10's >> heightened security. > > *sigh* > >> Currently I can debug with: >> a) sudo qtcreator (don't like this) >> b) First echoing 0 to /proc/sys/kernel/yama/ptrace_scope then running >> qtcreator > > Is any of that needed when using plain gdb? >From https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening I would think that only attaching to an arbitrary process should be blocked (for both Qt Creator and plain gdb), normal debugging from Qt Creator (i.e. starting the debugged process from Qt Creator) should still work (except perhaps for debugging an application that is "run in a terminal", since in this situation we explicitly "attach" gdb to the app that is run in the terminal). ++ Eike >> I'm looking for a solution where I could launch qtcreator without any extra >> gimmicks. >> Would setting setuid bit for qtcreator cut it? >> >> Oh, I also tried setcap cap_sys_prace=eip qtcreator but that didn't work >> because >> qtcreator cannot find libextensions. If I change the 'eip' to plain 'i', >> qtcreator starts >> but still debugging results in 'Ptrace: not permitted'. >> >> Any ideas? > > Ask the distributor? > > Andre' > ___ > Qt-creator mailing list > Qt-creator@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-creator ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Install support files together with plugin
Hi,
On Oct 16, 2010, at 5:14 PM, ext Tim Beaulen wrote:
> Hello,
>
> I'm creating a plugin that needs to install a couple of script files.
> In doing so I encountered a problem.
>
> First a question. Is it allowed to install these support files in
> share/qtcreator/myplugin/ ?
> Or is there some etiquette that says not to do that?
I wouldn't know a better place. But, if you consider to provide your plugin
cross-platform, you should notice that resources are at a different place on
Mac builds.
You should definitely use $$IDE_DATA_PATH/myplugin/scripts
and in you plugin sources Core::ICore::instance()->resourcePath() +
QLatin1String("/myplugin/scripts")
>
> In trying to install these files, I modified the .pro file of the
> plugin like so:
> Note: "..." replaces several other lines.
>
> 1. ...
> 2.
> 3. OTHER_FILES = ... \
> 4.tests/testscript.qs
> 5.
> 6. ...
> 7.
> 8. testscriptfiles.files += tests/testscript.qs
> 9. testscriptfiles.path = $$IDE_BUILD_TREE/share/qtcreator/myplugin/scripts
> 10. INSTALLS += testscriptfiles
INSTALLS creates an additional make target "make install". If you don't call
"make install" the files will not be copied. If you want to actually copy files
during the "make" step, you'll unfortunately need to do some fancy stuff,
similar to share/qtcreator/static.pro
/me wonders if we couldn't provide most of the stuff for this task as functions
in qtcreator.pri ?
++ Eike
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
