Hi Eike,
> > So looking in source code (src/plugins/debugger/gdb/gdbengine.cpp)
> > method void GdbEngine::setEnvironmentVariables() there's a loop that
> > sets or unsets every variable. But I couldn't understand what's the
> > criteria for any variable to have operation as EnvironmentItem::Unset
On Thu, 2 Jul 2020 12:17:09 -0300
Pablo Rogina wrote:
> again, by looking at the Application Output pane
I don't see how that would give you that information; we've already established
that gdb passes the arguments to the application at a later point.
Have you added debug code into your applica
> On Jul 2, 2020, at 23:00, Pablo Rogina wrote:
>
> Hi, this is a follow up to my issue. I guess I found what's happening
> but I was not able to fix it...
>
> I did run an external gdb-multiarch remote debug session in MI mode
> using all the commands QtCreator passes to the debugger. However
Hi, this is a follow up to my issue. I guess I found what's happening
but I was not able to fix it...
I did run an external gdb-multiarch remote debug session in MI mode
using all the commands QtCreator passes to the debugger. However, I
skipped the unset environment commands for all the env varia
Christian,
again, by looking at the Application Output pane, where I can see
gdbserver starting on remote device, the port number, etc.
But mostly by the fact that the debug session for my Qt application
CRASHES since the xcb plugin isn't loaded.
So somehow even when the proper -exec-args command
On Thu, 2 Jul 2020 09:37:51 -0300
Pablo Rogina wrote:
> I see. I'm not familiar with GDB/MI mode so that could be the right
> approach then, but the end result at least for me is that the
> arguments don't reach the remote program under debug
Again, how do you know that?
Christian
Hi Eike,
> src/plugins/debugger/gdb/gdbengine.cpp
thank you for pointing this out. I'll take a look to have a better idea.
> But the gdb engine used GDB/MI mode
> (http://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI.html) where
> -exec-arguments is correct (see "GDB/MI Program Context” section
> On Jul 1, 2020, at 22:55, Pablo Rogina wrote:
>
> checking the debugger log output I can see qtcreator is setting this:
> -exec-arguments -platform xcb
>
> but it looks like the proper way is to do this:
> set args -platform xcb
>
> how could I change what qtcreator sends to remote debugger
checking the debugger log output I can see qtcreator is setting this:
-exec-arguments -platform xcb
but it looks like the proper way is to do this:
set args -platform xcb
how could I change what qtcreator sends to remote debugger?
are those variables/commands hard-coded?
if so, what component sou
> > everything starts Ok but the command line arguments from the run
> > configuration aren't used
>
> How do you know that?
Because I can see the application Output pane and the command line
arguments don't show up, see my previous post please
___
Qt-cr
On Sun, 28 Jun 2020 20:18:49 -0300
Pablo Rogina wrote:
> However, if I intend to do debugging (F5) using gdb-multiarch
> everything starts Ok but the command line arguments from the run
> configuration aren't used
How do you know that?
Christian
___
Hi,
I've configured a kit for Raspberry Pi device, cross-compiled Qt and
setup a run configuration for the app to forward to local display and
use the XCB platform plugin, so I set command line arguments with
-platform xcb and it works fine when I do Run (Ctrl+R). The
application is deployed to th
12 matches
Mail list logo
