2022-08-19 15:59:36 +02:00
|
|
|
// Copyright (C) 2016 The Qt Company Ltd.
|
|
|
|
|
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GPL-3.0+ OR GPL-3.0 WITH Qt-GPL-exception-1.0
|
2008-12-02 15:08:31 +01:00
|
|
|
|
2010-09-22 16:20:08 +02:00
|
|
|
#include "logwindow.h"
|
2010-06-16 11:08:54 +02:00
|
|
|
|
2009-03-24 14:41:15 +01:00
|
|
|
#include "debuggeractions.h"
|
2013-01-10 12:40:50 +01:00
|
|
|
#include "debuggerengine.h"
|
2015-11-23 16:41:54 +01:00
|
|
|
#include "debuggericons.h"
|
2021-06-23 11:24:42 +02:00
|
|
|
#include "debuggerinternalconstants.h"
|
2022-07-05 15:37:08 +02:00
|
|
|
#include "debuggertr.h"
|
2008-12-02 12:01:29 +01:00
|
|
|
|
2012-02-15 10:42:41 +01:00
|
|
|
#include <QDebug>
|
|
|
|
|
#include <QTime>
|
2008-12-02 12:01:29 +01:00
|
|
|
|
2012-02-15 10:42:41 +01:00
|
|
|
#include <QHBoxLayout>
|
|
|
|
|
#include <QLabel>
|
|
|
|
|
#include <QMenu>
|
|
|
|
|
#include <QSyntaxHighlighter>
|
|
|
|
|
#include <QPlainTextEdit>
|
2013-07-12 13:23:51 +02:00
|
|
|
#include <QPushButton>
|
2012-02-15 10:42:41 +01:00
|
|
|
#include <QFileDialog>
|
2013-07-12 13:23:51 +02:00
|
|
|
#include <QToolButton>
|
2008-12-02 12:01:29 +01:00
|
|
|
|
|
|
|
|
#include <aggregation/aggregate.h>
|
2017-08-29 11:48:48 +02:00
|
|
|
|
|
|
|
|
#include <app/app_version.h>
|
|
|
|
|
|
2021-06-23 11:24:42 +02:00
|
|
|
#include <coreplugin/actionmanager/actionmanager.h>
|
2009-07-21 13:30:35 +02:00
|
|
|
#include <coreplugin/findplaceholder.h>
|
2010-03-16 16:55:56 +01:00
|
|
|
#include <coreplugin/minisplitter.h>
|
2014-01-13 16:17:34 +01:00
|
|
|
#include <coreplugin/find/basetextfind.h>
|
2008-12-02 12:01:29 +01:00
|
|
|
|
2012-08-23 14:26:24 +02:00
|
|
|
#include <utils/fancylineedit.h>
|
2013-03-25 17:13:18 +01:00
|
|
|
#include <utils/fileutils.h>
|
2015-03-19 20:44:18 +01:00
|
|
|
#include <utils/theme/theme.h>
|
2010-03-18 10:59:06 +01:00
|
|
|
|
2021-08-17 16:36:42 +02:00
|
|
|
using namespace Utils;
|
|
|
|
|
|
2022-07-05 15:37:08 +02:00
|
|
|
namespace Debugger::Internal {
|
2008-12-02 12:01:29 +01:00
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
GlobalLogWindow *theGlobalLog = nullptr;
|
|
|
|
|
|
|
|
|
|
static LogChannel channelForChar(QChar c)
|
|
|
|
|
{
|
|
|
|
|
switch (c.unicode()) {
|
|
|
|
|
case 'd': return LogDebug;
|
|
|
|
|
case 'w': return LogWarning;
|
|
|
|
|
case 'e': return LogError;
|
|
|
|
|
case '<': return LogInput;
|
|
|
|
|
case '>': return LogOutput;
|
|
|
|
|
case 's': return LogStatus;
|
|
|
|
|
case 't': return LogTime;
|
|
|
|
|
default: return LogMisc;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
QChar static charForChannel(int channel)
|
|
|
|
|
{
|
|
|
|
|
switch (channel) {
|
|
|
|
|
case LogDebug: return QLatin1Char('d');
|
|
|
|
|
case LogWarning: return QLatin1Char('w');
|
|
|
|
|
case LogError: return QLatin1Char('e');
|
|
|
|
|
case LogInput: return QLatin1Char('<');
|
|
|
|
|
case LogOutput: return QLatin1Char('>');
|
|
|
|
|
case LogStatus: return QLatin1Char('s');
|
|
|
|
|
case LogTime: return QLatin1Char('t');
|
|
|
|
|
case LogMisc:
|
|
|
|
|
default: return QLatin1Char(' ');
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static bool writeLogContents(const QPlainTextEdit *editor, QWidget *parent)
|
|
|
|
|
{
|
|
|
|
|
bool success = false;
|
|
|
|
|
while (!success) {
|
2022-07-05 15:37:08 +02:00
|
|
|
const FilePath filePath = FileUtils::getSaveFilePath(parent, Tr::tr("Log File"));
|
2021-08-17 16:36:42 +02:00
|
|
|
if (filePath.isEmpty())
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
break;
|
2021-08-17 16:36:42 +02:00
|
|
|
FileSaver saver(filePath, QIODevice::Text);
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
saver.write(editor->toPlainText().toUtf8());
|
|
|
|
|
if (saver.finalize(parent))
|
|
|
|
|
success = true;
|
|
|
|
|
}
|
|
|
|
|
return success;
|
|
|
|
|
}
|
|
|
|
|
|
2009-06-19 12:04:21 +02:00
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
//
|
|
|
|
|
// OutputHighlighter
|
|
|
|
|
//
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
|
|
|
|
|
class OutputHighlighter : public QSyntaxHighlighter
|
|
|
|
|
{
|
|
|
|
|
public:
|
|
|
|
|
OutputHighlighter(QPlainTextEdit *parent)
|
|
|
|
|
: QSyntaxHighlighter(parent->document()), m_parent(parent)
|
|
|
|
|
{}
|
|
|
|
|
|
|
|
|
|
private:
|
2018-07-23 22:28:49 +02:00
|
|
|
void highlightBlock(const QString &text) override
|
2009-06-19 12:04:21 +02:00
|
|
|
{
|
2015-03-19 20:44:18 +01:00
|
|
|
using Utils::Theme;
|
2009-06-19 12:04:21 +02:00
|
|
|
QTextCharFormat format;
|
2015-03-19 20:44:18 +01:00
|
|
|
Theme *theme = Utils::creatorTheme();
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
switch (channelForChar(text.isEmpty() ? QChar() : text.at(0))) {
|
2009-06-19 12:04:21 +02:00
|
|
|
case LogInput:
|
2015-03-19 20:44:18 +01:00
|
|
|
format.setForeground(theme->color(Theme::Debugger_LogWindow_LogInput));
|
2009-06-19 12:04:21 +02:00
|
|
|
setFormat(1, text.size(), format);
|
|
|
|
|
break;
|
|
|
|
|
case LogStatus:
|
2015-03-19 20:44:18 +01:00
|
|
|
format.setForeground(theme->color(Theme::Debugger_LogWindow_LogStatus));
|
2009-06-19 12:04:21 +02:00
|
|
|
setFormat(1, text.size(), format);
|
|
|
|
|
break;
|
2009-06-19 12:47:23 +02:00
|
|
|
case LogWarning:
|
2015-03-30 10:47:48 +03:00
|
|
|
format.setForeground(theme->color(Theme::OutputPanes_WarningMessageTextColor));
|
2009-06-19 12:47:23 +02:00
|
|
|
setFormat(1, text.size(), format);
|
|
|
|
|
break;
|
2009-06-19 12:04:21 +02:00
|
|
|
case LogError:
|
2015-03-30 10:47:48 +03:00
|
|
|
format.setForeground(theme->color(Theme::OutputPanes_ErrorMessageTextColor));
|
2009-06-19 12:04:21 +02:00
|
|
|
setFormat(1, text.size(), format);
|
|
|
|
|
break;
|
2009-07-06 09:54:24 +02:00
|
|
|
case LogTime:
|
2015-03-19 20:44:18 +01:00
|
|
|
format.setForeground(theme->color(Theme::Debugger_LogWindow_LogTime));
|
2009-07-06 09:54:24 +02:00
|
|
|
setFormat(1, text.size(), format);
|
|
|
|
|
break;
|
2009-06-19 12:04:21 +02:00
|
|
|
default:
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
QColor base = m_parent->palette().color(QPalette::Base);
|
|
|
|
|
format.setForeground(base);
|
|
|
|
|
format.setFontPointSize(1);
|
|
|
|
|
setFormat(0, 1, format);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
QPlainTextEdit *m_parent;
|
|
|
|
|
};
|
|
|
|
|
|
2010-02-04 14:03:07 +01:00
|
|
|
|
2008-12-02 12:01:29 +01:00
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
//
|
2010-02-04 14:03:07 +01:00
|
|
|
// InputHighlighter
|
|
|
|
|
//
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
|
|
|
|
|
class InputHighlighter : public QSyntaxHighlighter
|
|
|
|
|
{
|
|
|
|
|
public:
|
|
|
|
|
InputHighlighter(QPlainTextEdit *parent)
|
2012-06-27 22:19:20 +02:00
|
|
|
: QSyntaxHighlighter(parent->document())
|
2010-02-04 14:03:07 +01:00
|
|
|
{}
|
|
|
|
|
|
|
|
|
|
private:
|
2018-07-23 22:28:49 +02:00
|
|
|
void highlightBlock(const QString &text) override
|
2010-02-04 14:03:07 +01:00
|
|
|
{
|
2015-03-19 20:44:18 +01:00
|
|
|
using Utils::Theme;
|
|
|
|
|
Theme *theme = Utils::creatorTheme();
|
2018-10-07 22:38:47 +03:00
|
|
|
if (text.size() > 3 && text.at(2) == ':') {
|
2010-02-04 14:03:07 +01:00
|
|
|
QTextCharFormat format;
|
2015-03-19 20:44:18 +01:00
|
|
|
format.setForeground(theme->color(Theme::Debugger_LogWindow_LogTime));
|
2010-02-04 14:03:07 +01:00
|
|
|
setFormat(1, text.size(), format);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
//
|
|
|
|
|
// DebbuggerPane base class
|
2008-12-02 12:01:29 +01:00
|
|
|
//
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
|
2009-03-27 17:31:58 +01:00
|
|
|
class DebuggerPane : public QPlainTextEdit
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
|
|
|
|
public:
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
explicit DebuggerPane()
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
2010-03-18 16:23:52 +01:00
|
|
|
setFrameStyle(QFrame::NoFrame);
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
setSizePolicy(QSizePolicy::MinimumExpanding, QSizePolicy::MinimumExpanding);
|
|
|
|
|
|
2008-12-02 12:01:29 +01:00
|
|
|
m_clearContentsAction = new QAction(this);
|
2022-07-05 15:37:08 +02:00
|
|
|
m_clearContentsAction->setText(Tr::tr("Clear Contents"));
|
2008-12-02 12:01:29 +01:00
|
|
|
m_clearContentsAction->setEnabled(true);
|
|
|
|
|
|
|
|
|
|
m_saveContentsAction = new QAction(this);
|
2022-07-05 15:37:08 +02:00
|
|
|
m_saveContentsAction->setText(Tr::tr("Save Contents"));
|
2008-12-02 12:01:29 +01:00
|
|
|
m_saveContentsAction->setEnabled(true);
|
2015-02-12 13:50:54 +01:00
|
|
|
connect(m_saveContentsAction, &QAction::triggered,
|
|
|
|
|
this, &DebuggerPane::saveContents);
|
2008-12-02 12:01:29 +01:00
|
|
|
}
|
|
|
|
|
|
2018-07-23 22:28:49 +02:00
|
|
|
void contextMenuEvent(QContextMenuEvent *ev) override
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
|
|
|
|
QMenu *menu = createStandardContextMenu();
|
|
|
|
|
menu->addAction(m_clearContentsAction);
|
2010-05-25 15:24:21 +02:00
|
|
|
menu->addAction(m_saveContentsAction); // X11 clipboard is unreliable for long texts
|
2021-03-01 08:59:44 +01:00
|
|
|
menu->addAction(debuggerSettings()->logTimeStamps.action());
|
2021-06-23 11:24:42 +02:00
|
|
|
menu->addAction(Core::ActionManager::command(Constants::RELOAD_DEBUGGING_HELPERS)->action());
|
2009-03-24 14:41:15 +01:00
|
|
|
menu->addSeparator();
|
2021-03-01 08:59:44 +01:00
|
|
|
menu->addAction(debuggerSettings()->settingsDialog.action());
|
2008-12-02 12:01:29 +01:00
|
|
|
menu->exec(ev->globalPos());
|
|
|
|
|
delete menu;
|
|
|
|
|
}
|
|
|
|
|
|
2012-06-26 17:27:20 +02:00
|
|
|
void append(const QString &text)
|
|
|
|
|
{
|
|
|
|
|
const int N = 100000;
|
2013-02-27 16:12:28 +01:00
|
|
|
const int bc = blockCount();
|
|
|
|
|
if (bc > N) {
|
|
|
|
|
QTextDocument *doc = document();
|
|
|
|
|
QTextBlock block = doc->findBlockByLineNumber(bc * 9 / 10);
|
2012-06-26 17:27:20 +02:00
|
|
|
QTextCursor tc(block);
|
2013-02-27 16:12:28 +01:00
|
|
|
tc.movePosition(QTextCursor::Start, QTextCursor::KeepAnchor);
|
2012-06-26 17:27:20 +02:00
|
|
|
tc.removeSelectedText();
|
2013-02-27 16:12:28 +01:00
|
|
|
// Seems to be the only way to force shrinking of the
|
|
|
|
|
// allocated data.
|
|
|
|
|
QString contents = doc->toHtml();
|
|
|
|
|
doc->clear();
|
|
|
|
|
doc->setHtml(contents);
|
2012-06-26 17:27:20 +02:00
|
|
|
}
|
|
|
|
|
appendPlainText(text);
|
|
|
|
|
}
|
|
|
|
|
|
2013-07-31 20:46:37 +03:00
|
|
|
void clearUndoRedoStacks()
|
|
|
|
|
{
|
|
|
|
|
if (!isUndoRedoEnabled())
|
|
|
|
|
return;
|
|
|
|
|
setUndoRedoEnabled(false);
|
|
|
|
|
setUndoRedoEnabled(true);
|
|
|
|
|
}
|
2008-12-02 12:01:29 +01:00
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
QAction *clearContentsAction() const { return m_clearContentsAction; }
|
|
|
|
|
|
2015-02-12 13:50:54 +01:00
|
|
|
private:
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
void saveContents() { writeLogContents(this, this); }
|
2010-05-25 15:24:21 +02:00
|
|
|
|
2008-12-02 12:01:29 +01:00
|
|
|
QAction *m_clearContentsAction;
|
|
|
|
|
QAction *m_saveContentsAction;
|
|
|
|
|
};
|
|
|
|
|
|
2010-05-25 15:24:21 +02:00
|
|
|
|
2013-01-10 12:40:50 +01:00
|
|
|
|
2010-02-04 14:03:07 +01:00
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
//
|
|
|
|
|
// InputPane
|
|
|
|
|
//
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
|
2008-12-02 12:01:29 +01:00
|
|
|
class InputPane : public DebuggerPane
|
|
|
|
|
{
|
|
|
|
|
Q_OBJECT
|
|
|
|
|
public:
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
InputPane(LogWindow *logWindow)
|
2010-02-04 14:03:07 +01:00
|
|
|
{
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
connect(clearContentsAction(), &QAction::triggered,
|
|
|
|
|
logWindow, &LogWindow::clearContents);
|
2010-02-04 14:03:07 +01:00
|
|
|
(void) new InputHighlighter(this);
|
|
|
|
|
}
|
2008-12-02 12:01:29 +01:00
|
|
|
|
|
|
|
|
signals:
|
2011-12-13 12:28:38 +01:00
|
|
|
void executeLineRequested();
|
2008-12-02 12:01:29 +01:00
|
|
|
void clearContentsRequested();
|
|
|
|
|
void statusMessageRequested(const QString &, int);
|
|
|
|
|
void commandSelected(int);
|
|
|
|
|
|
|
|
|
|
private:
|
2018-07-23 22:28:49 +02:00
|
|
|
void keyPressEvent(QKeyEvent *ev) override
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
|
|
|
|
if (ev->modifiers() == Qt::ControlModifier && ev->key() == Qt::Key_Return)
|
2011-12-13 12:28:38 +01:00
|
|
|
emit executeLineRequested();
|
2008-12-02 12:01:29 +01:00
|
|
|
else if (ev->modifiers() == Qt::ControlModifier && ev->key() == Qt::Key_R)
|
|
|
|
|
emit clearContentsRequested();
|
|
|
|
|
else
|
2009-03-27 17:31:58 +01:00
|
|
|
QPlainTextEdit::keyPressEvent(ev);
|
2008-12-02 12:01:29 +01:00
|
|
|
}
|
|
|
|
|
|
2018-07-23 22:28:49 +02:00
|
|
|
void mouseDoubleClickEvent(QMouseEvent *ev) override
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
|
|
|
|
QString line = cursorForPosition(ev->pos()).block().text();
|
|
|
|
|
int n = 0;
|
2009-07-09 14:24:53 +02:00
|
|
|
|
|
|
|
|
// cut time string
|
2018-10-07 22:38:47 +03:00
|
|
|
if (line.size() > 18 && line.at(0) == '[')
|
2008-12-02 12:01:29 +01:00
|
|
|
line = line.mid(18);
|
|
|
|
|
//qDebug() << line;
|
2009-07-09 14:24:53 +02:00
|
|
|
|
2008-12-02 12:01:29 +01:00
|
|
|
for (int i = 0; i != line.size(); ++i) {
|
|
|
|
|
QChar c = line.at(i);
|
|
|
|
|
if (!c.isDigit())
|
|
|
|
|
break;
|
|
|
|
|
n = 10 * n + c.unicode() - '0';
|
2009-07-09 14:24:53 +02:00
|
|
|
}
|
2008-12-02 12:01:29 +01:00
|
|
|
emit commandSelected(n);
|
|
|
|
|
}
|
|
|
|
|
|
2018-07-23 22:28:49 +02:00
|
|
|
void focusInEvent(QFocusEvent *ev) override
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
2022-07-05 15:37:08 +02:00
|
|
|
emit statusMessageRequested(Tr::tr("Type Ctrl-<Return> to execute a line."), -1);
|
2009-03-27 17:31:58 +01:00
|
|
|
QPlainTextEdit::focusInEvent(ev);
|
2008-12-02 12:01:29 +01:00
|
|
|
}
|
|
|
|
|
|
2018-07-23 22:28:49 +02:00
|
|
|
void focusOutEvent(QFocusEvent *ev) override
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
|
|
|
|
emit statusMessageRequested(QString(), -1);
|
2009-03-27 17:31:58 +01:00
|
|
|
QPlainTextEdit::focusOutEvent(ev);
|
2008-12-02 12:01:29 +01:00
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
//
|
|
|
|
|
// CombinedPane
|
|
|
|
|
//
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
|
|
|
|
|
class CombinedPane : public DebuggerPane
|
|
|
|
|
{
|
|
|
|
|
public:
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
CombinedPane(LogWindow *logWindow)
|
2009-06-19 12:04:21 +02:00
|
|
|
{
|
2009-08-18 11:23:01 +02:00
|
|
|
(void) new OutputHighlighter(this);
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
connect(clearContentsAction(), &QAction::triggered,
|
|
|
|
|
logWindow, &LogWindow::clearContents);
|
2009-06-19 12:04:21 +02:00
|
|
|
}
|
2008-12-02 12:01:29 +01:00
|
|
|
|
|
|
|
|
void gotoResult(int i)
|
2009-07-09 14:24:53 +02:00
|
|
|
{
|
2018-10-07 22:38:47 +03:00
|
|
|
QString needle = QString::number(i) + '^';
|
|
|
|
|
QString needle2 = '>' + needle;
|
2013-06-20 09:31:15 +02:00
|
|
|
QString needle3 = QString::fromLatin1("dtoken(\"%1\")@").arg(i);
|
2008-12-02 12:01:29 +01:00
|
|
|
QTextCursor cursor(document());
|
|
|
|
|
do {
|
2013-06-20 09:31:15 +02:00
|
|
|
QTextCursor newCursor = document()->find(needle, cursor);
|
|
|
|
|
if (newCursor.isNull()) {
|
|
|
|
|
newCursor = document()->find(needle3, cursor);
|
|
|
|
|
if (newCursor.isNull())
|
|
|
|
|
break; // Not found.
|
|
|
|
|
}
|
|
|
|
|
cursor = newCursor;
|
2008-12-02 12:01:29 +01:00
|
|
|
const QString line = cursor.block().text();
|
2013-06-20 09:31:15 +02:00
|
|
|
if (line.startsWith(needle) || line.startsWith(needle2) || line.startsWith(needle3)) {
|
2008-12-02 12:01:29 +01:00
|
|
|
setFocus();
|
|
|
|
|
setTextCursor(cursor);
|
|
|
|
|
ensureCursorVisible();
|
|
|
|
|
cursor.movePosition(QTextCursor::Down, QTextCursor::KeepAnchor);
|
|
|
|
|
setTextCursor(cursor);
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
} while (cursor.movePosition(QTextCursor::Down));
|
|
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
//
|
|
|
|
|
// DebuggerOutputWindow
|
|
|
|
|
//
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
LogWindow::LogWindow(DebuggerEngine *engine)
|
|
|
|
|
: m_engine(engine)
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
2022-07-05 15:37:08 +02:00
|
|
|
setWindowTitle(Tr::tr("Debugger &Log"));
|
2018-10-07 22:38:47 +03:00
|
|
|
setObjectName("Log");
|
2008-12-02 12:01:29 +01:00
|
|
|
|
2011-12-13 12:28:38 +01:00
|
|
|
m_ignoreNextInputEcho = false;
|
|
|
|
|
|
2015-02-12 13:50:54 +01:00
|
|
|
auto m_splitter = new Core::MiniSplitter(Qt::Horizontal);
|
2010-03-16 16:55:56 +01:00
|
|
|
m_splitter->setParent(this);
|
2011-02-16 12:12:09 +01:00
|
|
|
|
|
|
|
|
// Mixed input/output.
|
2008-12-02 12:01:29 +01:00
|
|
|
m_combinedText = new CombinedPane(this);
|
|
|
|
|
m_combinedText->setReadOnly(true);
|
|
|
|
|
m_combinedText->setReadOnly(false);
|
|
|
|
|
|
2011-02-16 12:12:09 +01:00
|
|
|
// Input only.
|
2008-12-02 12:01:29 +01:00
|
|
|
m_inputText = new InputPane(this);
|
|
|
|
|
m_inputText->setReadOnly(false);
|
2011-02-16 12:12:09 +01:00
|
|
|
|
2012-08-23 14:26:24 +02:00
|
|
|
m_commandEdit = new Utils::FancyLineEdit(this);
|
2011-02-18 11:17:54 +01:00
|
|
|
m_commandEdit->setFrame(false);
|
2018-10-07 22:38:47 +03:00
|
|
|
m_commandEdit->setHistoryCompleter("DebuggerInput");
|
2013-07-12 13:23:51 +02:00
|
|
|
|
2015-02-12 13:50:54 +01:00
|
|
|
auto repeatButton = new QToolButton(this);
|
2016-04-20 16:12:42 +02:00
|
|
|
repeatButton->setIcon(Icons::STEP_OVER.icon());
|
2015-11-23 16:41:54 +01:00
|
|
|
repeatButton->setFixedSize(QSize(18, 18));
|
2022-07-05 15:37:08 +02:00
|
|
|
repeatButton->setToolTip(Tr::tr("Repeat last command for debug reasons."));
|
2013-07-12 13:23:51 +02:00
|
|
|
|
2015-02-12 13:50:54 +01:00
|
|
|
auto commandBox = new QHBoxLayout;
|
2013-07-12 13:23:51 +02:00
|
|
|
commandBox->addWidget(repeatButton);
|
2022-07-05 15:37:08 +02:00
|
|
|
commandBox->addWidget(new QLabel(Tr::tr("Command:"), this));
|
2011-02-16 12:12:09 +01:00
|
|
|
commandBox->addWidget(m_commandEdit);
|
2019-08-29 10:36:01 +02:00
|
|
|
commandBox->setContentsMargins(2, 2, 2, 2);
|
2011-02-16 12:12:09 +01:00
|
|
|
commandBox->setSpacing(6);
|
|
|
|
|
|
2015-02-12 13:50:54 +01:00
|
|
|
auto leftBox = new QVBoxLayout;
|
2011-02-16 12:12:09 +01:00
|
|
|
leftBox->addWidget(m_inputText);
|
|
|
|
|
leftBox->addItem(commandBox);
|
2019-08-29 10:36:01 +02:00
|
|
|
leftBox->setContentsMargins(0, 0, 0, 0);
|
2011-02-16 12:12:09 +01:00
|
|
|
leftBox->setSpacing(0);
|
|
|
|
|
|
2015-02-12 13:50:54 +01:00
|
|
|
auto leftDummy = new QWidget;
|
2011-02-16 12:12:09 +01:00
|
|
|
leftDummy->setLayout(leftBox);
|
|
|
|
|
|
|
|
|
|
m_splitter->addWidget(leftDummy);
|
2008-12-02 12:01:29 +01:00
|
|
|
m_splitter->addWidget(m_combinedText);
|
2009-10-01 16:22:43 +02:00
|
|
|
m_splitter->setStretchFactor(0, 1);
|
|
|
|
|
m_splitter->setStretchFactor(1, 3);
|
2008-12-02 12:01:29 +01:00
|
|
|
|
2015-02-12 13:50:54 +01:00
|
|
|
auto layout = new QVBoxLayout(this);
|
2019-08-29 10:36:01 +02:00
|
|
|
layout->setContentsMargins(0, 0, 0, 0);
|
2009-07-21 13:30:35 +02:00
|
|
|
layout->setSpacing(0);
|
2009-07-21 15:55:46 +02:00
|
|
|
layout->addWidget(m_splitter);
|
2009-07-21 13:30:35 +02:00
|
|
|
layout->addWidget(new Core::FindToolBarPlaceHolder(this));
|
2008-12-02 12:01:29 +01:00
|
|
|
setLayout(layout);
|
|
|
|
|
|
2015-02-12 13:50:54 +01:00
|
|
|
auto aggregate = new Aggregation::Aggregate;
|
2008-12-02 12:01:29 +01:00
|
|
|
aggregate->add(m_combinedText);
|
2014-01-13 16:17:34 +01:00
|
|
|
aggregate->add(new Core::BaseTextFind(m_combinedText));
|
2008-12-02 12:01:29 +01:00
|
|
|
|
|
|
|
|
aggregate = new Aggregation::Aggregate;
|
|
|
|
|
aggregate->add(m_inputText);
|
2014-01-13 16:17:34 +01:00
|
|
|
aggregate->add(new Core::BaseTextFind(m_inputText));
|
2008-12-02 12:01:29 +01:00
|
|
|
|
2016-04-19 22:49:23 +02:00
|
|
|
connect(m_inputText, &InputPane::statusMessageRequested,
|
|
|
|
|
this, &LogWindow::statusMessageRequested);
|
|
|
|
|
connect(m_inputText, &InputPane::commandSelected,
|
|
|
|
|
m_combinedText, &CombinedPane::gotoResult);
|
2015-02-12 13:50:54 +01:00
|
|
|
connect(m_commandEdit, &QLineEdit::returnPressed,
|
|
|
|
|
this, &LogWindow::sendCommand);
|
2016-04-19 22:49:23 +02:00
|
|
|
connect(m_inputText, &InputPane::executeLineRequested,
|
|
|
|
|
this, &LogWindow::executeLine);
|
2015-02-12 13:50:54 +01:00
|
|
|
connect(repeatButton, &QAbstractButton::clicked,
|
|
|
|
|
this, &LogWindow::repeatLastCommand);
|
2011-05-02 16:43:43 +02:00
|
|
|
|
2015-02-12 13:50:54 +01:00
|
|
|
connect(&m_outputTimer, &QTimer::timeout,
|
|
|
|
|
this, &LogWindow::doOutput);
|
2012-06-28 08:15:50 +02:00
|
|
|
|
2011-05-02 16:43:43 +02:00
|
|
|
setMinimumHeight(60);
|
2016-07-15 14:49:09 +02:00
|
|
|
|
|
|
|
|
showOutput(LogWarning,
|
2022-07-05 15:37:08 +02:00
|
|
|
Tr::tr("Note: This log contains possibly confidential information about your machine, "
|
2016-07-15 14:49:09 +02:00
|
|
|
"environment variables, in-memory data of the processes you are debugging, and more. "
|
2017-08-29 11:48:48 +02:00
|
|
|
"It is never transferred over the internet by %1, and only stored "
|
2016-07-15 14:49:09 +02:00
|
|
|
"to disk if you manually use the respective option from the context menu, or through "
|
2018-05-23 12:48:15 +02:00
|
|
|
"mechanisms that are not under the control of %1's Debugger plugin, "
|
|
|
|
|
"for instance in swap files, or other plugins you might use.\n"
|
2016-07-15 14:49:09 +02:00
|
|
|
"You may be asked to share the contents of this log when reporting bugs related "
|
|
|
|
|
"to debugger operation. In this case, make sure your submission does not "
|
2017-08-29 11:48:48 +02:00
|
|
|
"contain data you do not want to or you are not allowed to share.\n\n")
|
|
|
|
|
.arg(Core::Constants::IDE_DISPLAY_NAME));
|
2011-02-16 12:12:09 +01:00
|
|
|
}
|
|
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
LogWindow::~LogWindow()
|
|
|
|
|
{
|
|
|
|
|
disconnect(&m_outputTimer, &QTimer::timeout, this, &LogWindow::doOutput);
|
|
|
|
|
m_outputTimer.stop();
|
|
|
|
|
doOutput();
|
|
|
|
|
}
|
|
|
|
|
|
2011-12-13 12:28:38 +01:00
|
|
|
void LogWindow::executeLine()
|
|
|
|
|
{
|
|
|
|
|
m_ignoreNextInputEcho = true;
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
m_engine->executeDebuggerCommand(m_inputText->textCursor().block().text());
|
2011-12-13 12:28:38 +01:00
|
|
|
}
|
|
|
|
|
|
2013-07-12 13:23:51 +02:00
|
|
|
void LogWindow::repeatLastCommand()
|
|
|
|
|
{
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
m_engine->debugLastCommand();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
DebuggerEngine *LogWindow::engine() const
|
|
|
|
|
{
|
|
|
|
|
return m_engine;
|
2013-07-12 13:23:51 +02:00
|
|
|
}
|
|
|
|
|
|
2011-02-16 12:12:09 +01:00
|
|
|
void LogWindow::sendCommand()
|
|
|
|
|
{
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
if (m_engine->acceptsDebuggerCommands())
|
|
|
|
|
m_engine->executeDebuggerCommand(m_commandEdit->text());
|
2014-01-04 01:34:51 +01:00
|
|
|
else
|
2022-07-05 15:37:08 +02:00
|
|
|
showOutput(LogError, Tr::tr("User commands are not accepted in the current state."));
|
2010-12-16 12:05:48 +01:00
|
|
|
}
|
2008-12-02 12:01:29 +01:00
|
|
|
|
2010-09-22 16:20:08 +02:00
|
|
|
void LogWindow::showOutput(int channel, const QString &output)
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
|
|
|
|
if (output.isEmpty())
|
|
|
|
|
return;
|
2012-06-20 15:52:01 +02:00
|
|
|
|
|
|
|
|
const QChar cchar = charForChannel(channel);
|
2018-10-07 22:38:47 +03:00
|
|
|
const QChar nchar = '\n';
|
2012-06-20 15:52:01 +02:00
|
|
|
|
|
|
|
|
QString out;
|
|
|
|
|
out.reserve(output.size() + 1000);
|
|
|
|
|
|
2021-03-01 08:59:44 +01:00
|
|
|
if (output.at(0) != '~' && debuggerSettings()->logTimeStamps.value()) {
|
2012-06-20 15:52:01 +02:00
|
|
|
out.append(charForChannel(LogTime));
|
|
|
|
|
out.append(logTimeStamp());
|
|
|
|
|
out.append(nchar);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
for (int pos = 0, n = output.size(); pos < n; ) {
|
|
|
|
|
const int npos = output.indexOf(nchar, pos);
|
|
|
|
|
const int nnpos = npos == -1 ? n : npos;
|
|
|
|
|
const int l = nnpos - pos;
|
2020-09-18 13:05:37 +02:00
|
|
|
if (l != 6 || QStringView(output).mid(pos, 6) != QLatin1String("(gdb) ")) {
|
2012-06-20 15:52:01 +02:00
|
|
|
out.append(cchar);
|
|
|
|
|
if (l > 30000) {
|
|
|
|
|
// FIXME: QTextEdit asserts on really long lines...
|
2020-09-18 13:05:37 +02:00
|
|
|
out.append(output.mid(pos, 30000));
|
2018-10-07 22:38:47 +03:00
|
|
|
out.append(" [...] <cut off>\n");
|
2012-06-20 15:52:01 +02:00
|
|
|
} else {
|
2020-09-18 13:05:37 +02:00
|
|
|
out.append(output.mid(pos, l + 1));
|
2012-06-20 15:52:01 +02:00
|
|
|
}
|
2010-02-01 14:00:07 +01:00
|
|
|
}
|
2012-06-20 15:52:01 +02:00
|
|
|
pos = nnpos + 1;
|
2008-12-02 12:01:29 +01:00
|
|
|
}
|
2012-06-28 08:15:50 +02:00
|
|
|
if (!out.endsWith(nchar))
|
|
|
|
|
out.append(nchar);
|
|
|
|
|
|
|
|
|
|
m_queuedOutput.append(out);
|
2019-10-08 06:38:27 +02:00
|
|
|
// flush the output if it exceeds 16k to prevent out of memory exceptions on regular output
|
|
|
|
|
if (m_queuedOutput.size() > 16 * 1024) {
|
|
|
|
|
m_outputTimer.stop();
|
|
|
|
|
doOutput();
|
|
|
|
|
} else {
|
|
|
|
|
m_outputTimer.setSingleShot(true);
|
|
|
|
|
m_outputTimer.start(80);
|
|
|
|
|
}
|
2012-06-28 08:15:50 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void LogWindow::doOutput()
|
|
|
|
|
{
|
|
|
|
|
if (m_queuedOutput.isEmpty())
|
|
|
|
|
return;
|
|
|
|
|
|
2019-10-10 08:22:19 +02:00
|
|
|
if (theGlobalLog)
|
|
|
|
|
theGlobalLog->doOutput(m_queuedOutput);
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
|
2012-06-28 08:15:50 +02:00
|
|
|
QTextCursor cursor = m_combinedText->textCursor();
|
|
|
|
|
const bool atEnd = cursor.atEnd();
|
|
|
|
|
|
|
|
|
|
m_combinedText->append(m_queuedOutput);
|
|
|
|
|
m_queuedOutput.clear();
|
2012-06-20 15:52:01 +02:00
|
|
|
|
2009-12-17 12:23:01 +01:00
|
|
|
if (atEnd) {
|
2012-06-20 15:52:01 +02:00
|
|
|
cursor.movePosition(QTextCursor::End);
|
2009-12-17 12:23:01 +01:00
|
|
|
m_combinedText->setTextCursor(cursor);
|
|
|
|
|
m_combinedText->ensureCursorVisible();
|
|
|
|
|
}
|
2008-12-02 12:01:29 +01:00
|
|
|
}
|
|
|
|
|
|
2010-09-22 16:20:08 +02:00
|
|
|
void LogWindow::showInput(int channel, const QString &input)
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
2009-07-13 17:35:17 +02:00
|
|
|
Q_UNUSED(channel)
|
2011-12-13 12:28:38 +01:00
|
|
|
if (m_ignoreNextInputEcho) {
|
|
|
|
|
m_ignoreNextInputEcho = false;
|
|
|
|
|
QTextCursor cursor = m_inputText->textCursor();
|
|
|
|
|
cursor.movePosition(QTextCursor::Down);
|
|
|
|
|
cursor.movePosition(QTextCursor::EndOfLine);
|
|
|
|
|
m_inputText->setTextCursor(cursor);
|
|
|
|
|
return;
|
|
|
|
|
}
|
2021-03-01 08:59:44 +01:00
|
|
|
if (debuggerSettings()->logTimeStamps.value())
|
2012-06-26 17:27:20 +02:00
|
|
|
m_inputText->append(logTimeStamp());
|
|
|
|
|
m_inputText->append(input);
|
2008-12-02 12:01:29 +01:00
|
|
|
QTextCursor cursor = m_inputText->textCursor();
|
|
|
|
|
cursor.movePosition(QTextCursor::End);
|
|
|
|
|
m_inputText->setTextCursor(cursor);
|
|
|
|
|
m_inputText->ensureCursorVisible();
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
|
|
|
|
|
theGlobalLog->doInput(input);
|
2008-12-02 12:01:29 +01:00
|
|
|
}
|
|
|
|
|
|
2010-09-22 16:20:08 +02:00
|
|
|
void LogWindow::clearContents()
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
|
|
|
|
m_combinedText->clear();
|
|
|
|
|
m_inputText->clear();
|
|
|
|
|
}
|
|
|
|
|
|
2010-09-22 16:20:08 +02:00
|
|
|
void LogWindow::setCursor(const QCursor &cursor)
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
2010-07-21 12:18:50 +02:00
|
|
|
m_combinedText->viewport()->setCursor(cursor);
|
|
|
|
|
m_inputText->viewport()->setCursor(cursor);
|
2008-12-02 12:01:29 +01:00
|
|
|
QWidget::setCursor(cursor);
|
|
|
|
|
}
|
|
|
|
|
|
2010-09-22 16:20:08 +02:00
|
|
|
QString LogWindow::combinedContents() const
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
|
|
|
|
return m_combinedText->toPlainText();
|
|
|
|
|
}
|
|
|
|
|
|
2010-09-22 16:20:08 +02:00
|
|
|
QString LogWindow::inputContents() const
|
2008-12-02 12:01:29 +01:00
|
|
|
{
|
|
|
|
|
return m_inputText->toPlainText();
|
|
|
|
|
}
|
|
|
|
|
|
2013-07-31 20:46:37 +03:00
|
|
|
void LogWindow::clearUndoRedoStacks()
|
|
|
|
|
{
|
|
|
|
|
m_inputText->clearUndoRedoStacks();
|
|
|
|
|
m_combinedText->clearUndoRedoStacks();
|
|
|
|
|
}
|
|
|
|
|
|
2010-09-22 16:20:08 +02:00
|
|
|
QString LogWindow::logTimeStamp()
|
2010-08-23 14:27:24 +02:00
|
|
|
{
|
|
|
|
|
// Cache the last log time entry by ms. If time progresses,
|
|
|
|
|
// report the difference to the last time stamp in ms.
|
2018-10-07 22:38:47 +03:00
|
|
|
static const QString logTimeFormat("hh:mm:ss.zzz");
|
2010-08-23 14:27:24 +02:00
|
|
|
static QTime lastTime = QTime::currentTime();
|
|
|
|
|
static QString lastTimeStamp = lastTime.toString(logTimeFormat);
|
|
|
|
|
|
|
|
|
|
const QTime currentTime = QTime::currentTime();
|
|
|
|
|
if (currentTime != lastTime) {
|
|
|
|
|
const int elapsedMS = lastTime.msecsTo(currentTime);
|
|
|
|
|
lastTime = currentTime;
|
|
|
|
|
lastTimeStamp = lastTime.toString(logTimeFormat);
|
|
|
|
|
// Append time elapsed
|
|
|
|
|
QString rc = lastTimeStamp;
|
2018-10-07 22:38:47 +03:00
|
|
|
rc += " [";
|
2010-08-23 14:27:24 +02:00
|
|
|
rc += QString::number(elapsedMS);
|
2018-10-07 22:38:47 +03:00
|
|
|
rc += "ms]";
|
2010-08-23 14:27:24 +02:00
|
|
|
return rc;
|
|
|
|
|
}
|
|
|
|
|
return lastTimeStamp;
|
|
|
|
|
}
|
|
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
//
|
|
|
|
|
// GlobalLogWindow
|
|
|
|
|
//
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
|
|
|
|
|
|
GlobalLogWindow::GlobalLogWindow()
|
2010-11-02 16:14:00 +01:00
|
|
|
{
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
theGlobalLog = this;
|
|
|
|
|
|
2022-07-05 15:37:08 +02:00
|
|
|
setWindowTitle(Tr::tr("Global Debugger &Log"));
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
setObjectName("GlobalLog");
|
|
|
|
|
|
|
|
|
|
auto m_splitter = new Core::MiniSplitter(Qt::Horizontal);
|
|
|
|
|
m_splitter->setParent(this);
|
|
|
|
|
|
|
|
|
|
m_rightPane = new DebuggerPane;
|
|
|
|
|
m_rightPane->setReadOnly(true);
|
|
|
|
|
|
|
|
|
|
m_leftPane = new DebuggerPane;
|
|
|
|
|
m_leftPane->setReadOnly(true);
|
|
|
|
|
|
|
|
|
|
m_splitter->addWidget(m_leftPane);
|
|
|
|
|
m_splitter->addWidget(m_rightPane);
|
|
|
|
|
m_splitter->setStretchFactor(0, 1);
|
|
|
|
|
m_splitter->setStretchFactor(1, 3);
|
|
|
|
|
|
|
|
|
|
auto layout = new QVBoxLayout(this);
|
2019-08-29 10:36:01 +02:00
|
|
|
layout->setContentsMargins(0, 0, 0, 0);
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
layout->setSpacing(0);
|
|
|
|
|
layout->addWidget(m_splitter);
|
|
|
|
|
layout->addWidget(new Core::FindToolBarPlaceHolder(this));
|
|
|
|
|
setLayout(layout);
|
|
|
|
|
|
|
|
|
|
auto aggregate = new Aggregation::Aggregate;
|
|
|
|
|
aggregate->add(m_rightPane);
|
|
|
|
|
aggregate->add(new Core::BaseTextFind(m_rightPane));
|
|
|
|
|
|
|
|
|
|
aggregate = new Aggregation::Aggregate;
|
|
|
|
|
aggregate->add(m_leftPane);
|
|
|
|
|
aggregate->add(new Core::BaseTextFind(m_leftPane));
|
|
|
|
|
|
|
|
|
|
connect(m_leftPane->clearContentsAction(), &QAction::triggered,
|
|
|
|
|
this, &GlobalLogWindow::clearContents);
|
|
|
|
|
connect(m_rightPane->clearContentsAction(), &QAction::triggered,
|
|
|
|
|
this, &GlobalLogWindow::clearContents);
|
2010-11-02 16:14:00 +01:00
|
|
|
}
|
|
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
GlobalLogWindow::~GlobalLogWindow()
|
2011-12-21 14:02:52 +01:00
|
|
|
{
|
2019-10-10 08:22:19 +02:00
|
|
|
theGlobalLog = nullptr;
|
2011-12-21 14:02:52 +01:00
|
|
|
}
|
|
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
void GlobalLogWindow::doOutput(const QString &output)
|
2011-12-21 14:02:52 +01:00
|
|
|
{
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
QTextCursor cursor = m_rightPane->textCursor();
|
|
|
|
|
const bool atEnd = cursor.atEnd();
|
|
|
|
|
|
|
|
|
|
m_rightPane->append(output);
|
|
|
|
|
|
|
|
|
|
if (atEnd) {
|
|
|
|
|
cursor.movePosition(QTextCursor::End);
|
|
|
|
|
m_rightPane->setTextCursor(cursor);
|
|
|
|
|
m_rightPane->ensureCursorVisible();
|
2011-12-21 14:02:52 +01:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
void GlobalLogWindow::doInput(const QString &input)
|
|
|
|
|
{
|
2021-03-01 08:59:44 +01:00
|
|
|
if (debuggerSettings()->logTimeStamps.value())
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
m_leftPane->append(LogWindow::logTimeStamp());
|
|
|
|
|
m_leftPane->append(input);
|
|
|
|
|
QTextCursor cursor = m_leftPane->textCursor();
|
|
|
|
|
cursor.movePosition(QTextCursor::End);
|
|
|
|
|
m_leftPane->setTextCursor(cursor);
|
|
|
|
|
m_leftPane->ensureCursorVisible();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void GlobalLogWindow::clearContents()
|
|
|
|
|
{
|
|
|
|
|
m_rightPane->clear();
|
|
|
|
|
m_leftPane->clear();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void GlobalLogWindow::setCursor(const QCursor &cursor)
|
|
|
|
|
{
|
|
|
|
|
m_rightPane->viewport()->setCursor(cursor);
|
|
|
|
|
m_leftPane->viewport()->setCursor(cursor);
|
|
|
|
|
QWidget::setCursor(cursor);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void GlobalLogWindow::clearUndoRedoStacks()
|
|
|
|
|
{
|
|
|
|
|
m_leftPane->clearUndoRedoStacks();
|
|
|
|
|
m_rightPane->clearUndoRedoStacks();
|
|
|
|
|
}
|
|
|
|
|
|
2022-07-05 15:37:08 +02:00
|
|
|
} // namespace Debugger::Internal
|
2010-09-22 16:20:08 +02:00
|
|
|
|
|
|
|
|
#include "logwindow.moc"
|