Commit d7131841 authored by Jonathan Marten's avatar Jonathan Marten

Correct assert in BacktraceGenerator::start()

The original code said

  Q_ASSERT(m_proc == NULL && m_temp == NULL);

which agrees with the comment - ensure that the two pointers are null.
Commit abb6999b unfortunately reversed the test, which means that
DrKonqi crashes as soon as it tries to start :-(

The assert is split up so that, if one is hit, it will be obvious which
pointer is at fault.
parent 0dc5d800
......@@ -66,7 +66,8 @@ BacktraceGenerator::~BacktraceGenerator()
bool BacktraceGenerator::start()
{
//they should always be null before entering this function.
Q_ASSERT(m_proc && m_temp);
Q_ASSERT(!m_proc);
Q_ASSERT(!m_temp);
m_parsedBacktrace.clear();
m_state = Loading;
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment