[kdev-python] [Bug 372454] Crash while editing

2018-10-26 Thread Andrew Crouthamel
https://bugs.kde.org/show_bug.cgi?id=372454

Andrew Crouthamel  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #5 from Andrew Crouthamel  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The
bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki
located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 372454] Crash while editing

2018-09-26 Thread Andrew Crouthamel
https://bugs.kde.org/show_bug.cgi?id=372454

Andrew Crouthamel  changed:

   What|Removed |Added

   Keywords||triaged

--- Comment #4 from Andrew Crouthamel  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information as soon as possible and set the bug
status as REPORTED. Due to regular bug tracker maintenance, if the bug is still
in NEEDSINFO status with no change in 30 days, the bug will be closed as
RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki
located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug
status as REPORTED so that the KDE team knows that the bug is ready to be
confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 372454] Crash while editing

2016-12-18 Thread Alex Maystrenko
https://bugs.kde.org/show_bug.cgi?id=372454

Alex Maystrenko  changed:

   What|Removed |Added

 CC||alexeyt...@gmail.com

--- Comment #3 from Alex Maystrenko  ---
I have the same crash, it happens often while editing. I have rather big
project, but according to the log it happens when KDevelop parses the file I am
editing.

I think this crash is at the same point at duchain/expressionvisitor.cpp:70.
Does the frame #0 in gdb means bad pointer dereference? Or do I need to compile
other packages with debug symbols?

Thread 6 "KDevelop::Compl" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffb8b46700 (LWP 18669)]
0x7fff9823b300 in ?? ()
(gdb) 
(gdb) bt
#0  0x7fff9823b300 in  ()
#1  0x7fffb8b89a2f in
Python::ExpressionVisitor::ExpressionVisitor(KDevelop::DUContext const*)
(this=0x7fffb4008d00, ctx=)
at
/aur/kdevelop-python/src/kdev-python-5.0.3/duchain/expressionvisitor.cpp:70
#2  0x7fffb8dfea49 in Python::visitorForString(QString,
KDevelop::DUContext*, KDevelop::CursorInRevision) (str=...,
context=context@entry=
0x7fff9829f7d0, scanUntil=scanUntil@entry=...) at
/aur/kdevelop-python/src/kdev-python-5.0.3/codecompletion/context.cpp:84
#3  0x7fffb8e07707 in
Python::PythonCodeCompletionContext::memberAccessItems()
(this=this@entry=0x7fffb403fb00)
at
/aur/kdevelop-python/src/kdev-python-5.0.3/codecompletion/context.cpp:337
#4  0x7fffb8e080cb in
Python::PythonCodeCompletionContext::completionItems(bool&, bool)
(this=this@entry=0x7fffb403fb00, abort=@0xeb6ce0: false,
fullCompletion=fullCompletion@entry=false) at
/aur/kdevelop-python/src/kdev-python-5.0.3/codecompletion/context.cpp:593
#5  0x72e8a139 in
KDevelop::CodeCompletionWorker::computeCompletions(KDevelop::DUChainPointer,
KTextEditor::Cursor const&, QString, KTextEditor::Range const&, QString const&)
(this=0xeb6cc0, context=..., position=..., followingText=..., contextRange=...,
contextText=...)
at
/aur/kdevplatform/src/kdevplatform-5.0.3/language/codecompletion/codecompletionworker.cpp:167
#6  0x72e89ba2 in
KDevelop::CodeCompletionWorker::computeCompletions(KDevelop::DUChainPointer,
KTextEditor::Cursor const&, KTextEditor::View*) (this=0xeb6cc0, context=...,
position=..., view=0xfc9680)
at
/aur/kdevplatform/src/kdevplatform-5.0.3/language/codecompletion/codecompletionworker.cpp:129
#7  0x72e906a1 in QtPrivate::FunctorCall, QtPrivate::List, void, void
(KDevelop::CodeCompletionWorker::*)(KDevelop::DUChainPointer,
KTextEditor::Cursor const&, KTextEditor::View*)>::call(void
(KDevelop::CodeCompletionWorker::*)(KDevelop::DUChainPointer,
KTextEditor::Cursor const&, KTextEditor::View*),
KDevelop::CodeCompletionWorker*, void**) (arg=, o=, f=)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:507


OS: Arch-linux, kdevelop 5.0.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 372454] Crash while editing

2016-11-14 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=372454

Aleix Pol  changed:

   What|Removed |Added

 CC||aleix...@kde.org
 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Aleix Pol  ---
Not now, if I reproduce, I'll include it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 372454] Crash while editing

2016-11-13 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=372454

Sven Brauch  changed:

   What|Removed |Added

   Target Milestone|--- |5.0.3
Product|kdevelop|kdev-python
  Component|general |general
   Assignee|kdevelop-bugs-n...@kde.org  |m...@svenbrauch.de
 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Do you have a code snippet where it crashes?

-- 
You are receiving this mail because:
You are watching all bug changes.