« previous next »
Pages: 1 2 3 4 [5] 6 7 8   Go Down

Author Topic: Is CC crash, or Debugger plugin?  (Read 73095 times)

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: Is CC crash, or Debugger plugin?
« Reply #60 on: August 02, 2011, 06:43:28 pm »
Quote from: oBFusCATed on August 02, 2011, 05:51:15 pm
Try from the command line, there is more output there.

And you're trying it on a big project for long time? If you just start C::B move around for a minute and quit, you'll find nothing.
Here is the full log.
There has some leak report:
Quote
==18616== 176 bytes in 11 blocks are definitely lost in loss record 8,834 of 10,856
==18616==    at 0x4C279FC: calloc (vg_replace_malloc.c:467)
==18616==    by 0xA5C5AB9: g_malloc0 (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.2800.6)
==18616==    by 0x151A6967: ??? (in /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so)
==18616==    by 0x151A75EA: ??? (in /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so)
==18616==    by 0x84BEBCB: gtk_menu_shell_insert (in /usr/lib/libgtk-x11-2.0.so.0.2400.4)
==18616==    by 0x5FDDFD4: wxChoice::GtkAddHelper(_GtkWidget*, unsigned int, wxString const&) (in /usr/lib/libwx_gtk2u_core-2.8.so.0.7.0)
==18616==    by 0x1C85BBCD: wxItemContainer::Append(wxString const&) (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x1C8803F3: CodeCompletion::ParseFunctionsAndFillToolbar(bool) (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x1C884F0F: CodeCompletion::OnParserEnd(wxCommandEvent&) (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x68C4AD4: wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) (in /usr/lib/libwx_baseu-2.8.so.0.7.0)
==18616==    by 0x68C4C5B: wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) (in /usr/lib/libwx_baseu-2.8.so.0.7.0)
==18616==    by 0x68C4F93: wxEvtHandler::ProcessEvent(wxEvent&) (in /usr/lib/libwx_baseu-2.8.so.0.7.0)
But I don't got the reason.

Quote
==18616==
==18616== 320 bytes in 1 blocks are possibly lost in loss record 9,185 of 10,856
==18616==    at 0x4C279FC: calloc (vg_replace_malloc.c:467)
==18616==    by 0x4011868: _dl_allocate_tls (dl-tls.c:300)
==18616==    by 0x7DC8871: pthread_create@@GLIBC_2.2.5 (allocatestack.c:570)
==18616==    by 0x68C2F10: wxThread::Create(unsigned int) (in /usr/lib/libwx_baseu-2.8.so.0.7.0)
==18616==    by 0x6D63120: cbThreadPool::_SetConcurrentThreads(int) (in /home/loaden/DengYC/CodeBlocks/src/output/libcodeblocks.so)
==18616==    by 0x6D62F3C: cbThreadPool::SetConcurrentThreads(int) (in /home/loaden/DengYC/CodeBlocks/src/output/libcodeblocks.so)
==18616==    by 0x1C8CA584: cbThreadPool::cbThreadPool(wxEvtHandler*, int, int, unsigned int) (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x1C8C4FE2: Parser::Parser(wxEvtHandler*, cbProject*) (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x1C89FC19: NativeParser::NativeParser() (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x1C874508: CodeCompletion::CodeCompletion() (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x1C88B05A: PluginRegistrant<CodeCompletion>::CreatePlugin() (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x6E04BFE: PluginManager::LoadPlugin(wxString const&) (in /home/loaden/DengYC/CodeBlocks/src/output/libcodeblocks.so)

Quote
==18616== 320 bytes in 1 blocks are possibly lost in loss record 9,187 of 10,856
==18616==    at 0x4C279FC: calloc (vg_replace_malloc.c:467)
==18616==    by 0x4011868: _dl_allocate_tls (dl-tls.c:300)
==18616==    by 0x7DC8871: pthread_create@@GLIBC_2.2.5 (allocatestack.c:570)
==18616==    by 0x68C2F10: wxThread::Create(unsigned int) (in /usr/lib/libwx_baseu-2.8.so.0.7.0)
==18616==    by 0x6D63120: cbThreadPool::_SetConcurrentThreads(int) (in /home/loaden/DengYC/CodeBlocks/src/output/libcodeblocks.so)
==18616==    by 0x6D62F3C: cbThreadPool::SetConcurrentThreads(int) (in /home/loaden/DengYC/CodeBlocks/src/output/libcodeblocks.so)
==18616==    by 0x1C8CA584: cbThreadPool::cbThreadPool(wxEvtHandler*, int, int, unsigned int) (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x1C8C4FE2: Parser::Parser(wxEvtHandler*, cbProject*) (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x1C8A6B74: NativeParser::CreateParser(cbProject*) (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x1C8B21B6: NativeParser::OnParsingOneByOneTimer(wxTimerEvent&) (in /home/loaden/DengYC/CodeBlocks/src/output/share/codeblocks/plugins/libcodecompletion.so)
==18616==    by 0x68C4AD4: wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) (in /usr/lib/libwx_baseu-2.8.so.0.7.0)
==18616==    by 0x68C4C5B: wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) (in /usr/lib/libwx_baseu-2.8.so.0.7.0)

[attachment deleted by admin]
« Last Edit: August 02, 2011, 06:45:46 pm by Loaden »
Logged

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Is CC crash, or Debugger plugin?
« Reply #61 on: August 02, 2011, 07:33:36 pm »
Loaden: memory leak detection in wx apps is impossible. Look only for invalid read and writes.

Edit: I cannot extract the last two files.
« Last Edit: August 02, 2011, 07:40:11 pm by oBFusCATed »
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Is CC crash, or Debugger plugin?
« Reply #62 on: August 02, 2011, 08:52:59 pm »
Quote from: oBFusCATed on August 02, 2011, 07:33:36 pm
Edit: I cannot extract the last two files.
You'll need a quite recent (beta) version of 7-Zip.
Logged
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Is CC crash, or Debugger plugin?
« Reply #63 on: August 02, 2011, 09:21:15 pm »
Code
7-Zip (A) [64] 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18
p7zip Version 9.20 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,4 CPUs)
Isn't this new enough? If it isn't 7zip is useless...
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline ouch

  • Almost regular
  • **
  • Posts: 223
Re: Is CC crash, or Debugger plugin?
« Reply #64 on: August 02, 2011, 09:25:47 pm »
You need the beta version, not the release version of 7-zip.
Logged

Offline Jenna

  • Administrator
  • Lives here!
  • *****
  • Posts: 7255
Re: Is CC crash, or Debugger plugin?
« Reply #65 on: August 02, 2011, 09:33:57 pm »
7z can create volumes, with a maximum size, useful if there is a size-limit like for the attachements on the forum.

I don't know the correct way to unpack on linux, maybe there is some commandline for it, but I did not fiind.
What works: cp test.log.7z.001.7z test.log.7z and cat test.log.7z.002.7z >> test.log.7z and the unpack test.log.7z as usual.
Logged

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Is CC crash, or Debugger plugin?
« Reply #66 on: August 02, 2011, 10:14:22 pm »
Hm, as far as I know we advise people to upload their files elsewhere, because we are space limited. So Loaden, please don't use this useless 7zip archiver, but use a paste bin service :)
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: Is CC crash, or Debugger plugin?
« Reply #67 on: August 03, 2011, 03:28:15 am »
Quote from: jens on August 02, 2011, 09:33:57 pm
7z can create volumes, with a maximum size, useful if there is a size-limit like for the attachements on the forum.

I don't know the correct way to unpack on linux, maybe there is some commandline for it, but I did not fiind.
What works: cp test.log.7z.001.7z test.log.7z and cat test.log.7z.002.7z >> test.log.7z and the unpack test.log.7z as usual.
Sorry, I should say how to unpack it.
On Linux: RENAME test.log.7z.001.7z TO test.log.7z.001 , and RENAME test.log.7z.002.7z TO test.log.7z.002, Put them in the same folder, Then unpack test.log.7z.001

I can't upload "001" or "002" file types, so...
By the way, can we add "xz" file types for attachments?
Logged

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Is CC crash, or Debugger plugin?
« Reply #68 on: August 03, 2011, 06:55:22 am »
Quote from: Loaden on August 03, 2011, 03:28:15 am
By the way, can we add "xz" file types for attachments?
Yes, but what is a "xz" file?
Logged
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: Is CC crash, or Debugger plugin?
« Reply #69 on: August 03, 2011, 07:04:15 am »
Logged

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Is CC crash, or Debugger plugin?
« Reply #70 on: August 03, 2011, 07:09:11 am »
Quote from: Loaden on August 03, 2011, 07:04:15 am
http://en.wikipedia.org/wiki/Xz
Another one? I already got used to tar.bz, bz2, zip, 7z, rar, ace... what else will follow? And as HDD disk space it cheap these days, why saving a few more bytes? I think we should stick with the formats that are supported by one extraction tool, namely 7z , (Win)ZIP or (Win)RAR. This will avoid forum messages like "What filetype is xz" and "I cannot open file "xz" in Code::Blocks (no, it's an archive :shock:) and "what tool do I need to extract "xz"? and alike. ;-) :lol:
Logged
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: Is CC crash, or Debugger plugin?
« Reply #71 on: August 03, 2011, 07:15:57 am »
Quote from: MortenMacFly on August 03, 2011, 07:09:11 am
Quote from: Loaden on August 03, 2011, 07:04:15 am
http://en.wikipedia.org/wiki/Xz
Another one? I already got used to tar.bz, bz2, zip, 7z, rar, ace... what else will follow? And as HDD disk space it cheap these days, why saving a few more bytes? I think we should stick with the formats that are supported by one extraction tool, namely 7z , (Win)ZIP or (Win)RAR. This will avoid forum messages like "What filetype is xz" and "I cannot open file "xz" in Code::Blocks (no, it's an archive :shock:) and "what tool do I need to extract "xz"? and alike. ;-) :lol:
Because the forum attachment size is limited to 128KB, and XZ has a higher compression ratio.
Logged

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Is CC crash, or Debugger plugin?
« Reply #72 on: August 03, 2011, 07:21:07 am »
Quote from: Loaden on August 03, 2011, 07:15:57 am
Because the forum attachment size is limited to 128KB, and XZ has a higher compression ratio.
Harhar... than it's easy: Use an external file sharing service for files > 128KB. ;-)
Logged
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Is CC crash, or Debugger plugin?
« Reply #73 on: August 17, 2011, 04:39:53 pm »
Another deadlock:

Code
(gdb) bt
#0  0x000000373d60d4c4 in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x000000373d608e1a in _L_lock_1034 () from /lib64/libpthread.so.0
#2  0x000000373d608cdc in pthread_mutex_lock () from /lib64/libpthread.so.0
#3  0x0000003744cfa3e9 in wxMutexInternal::Lock (this=<value optimized out>) at ./src/unix/threadpsx.cpp:248
#4  0x00002b97f97bf88b in wxCriticalSection::Enter (this=0x2aaab3e99a80) at /usr/include/wx-2.8/wx/thread.h:271
#5  0x00002b97f97bf8b5 in wxCriticalSectionLocker::wxCriticalSectionLocker (this=0x7fffd1edfff0, cs=...) at /usr/include/wx-2.8/wx/thread.h:286
#6  0x00002aaab3c030d7 in Parser::IsFileParsed (this=0xddc5040, filename=...) at parser/parser.cpp:1270
#7  0x00002aaab3bf25d0 in NativeParser::GetProjectByFilename (this=0xcd5e620, filename=...) at nativeparser.cpp:286
#8  0x00002aaab3bb9ace in CodeCompletion::OnReparsingTimer (this=0xcd5e5a0, event=...) at codecompletion.cpp:1898
#9  0x0000003744cfcbff in wxEvtHandler::ProcessEventIfMatches (entry=<value optimized out>, handler=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1239
#10 0x0000003744cfcd9f in wxEventHashTable::HandleEvent (this=<value optimized out>, event=<value optimized out>, self=<value optimized out>) at ./src/common/event.cpp:906
#11 0x0000003744cfcee9 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1301
#12 0x0000003b39af2106 in wxTimerBase::Notify (this=<value optimized out>) at ./src/common/timercmn.cpp:57
#13 0x0000003b399ed2e3 in timeout_callback (data=<value optimized out>) at ./src/gtk/timer.cpp:45
#14 0x000000373ee2d2bb in ?? () from /lib64/libglib-2.0.so.0
#15 0x000000373ee2cdb4 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#16 0x000000373ee2fc0d in ?? () from /lib64/libglib-2.0.so.0
#17 0x000000373ee2ff1a in g_main_loop_run () from /lib64/libglib-2.0.so.0
#18 0x0000003b3872aa63 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0
#19 0x0000003b399e456d in wxEventLoop::Run (this=<value optimized out>) at ./src/gtk/evtloop.cpp:76
#20 0x0000003b39a3b5d1 in wxDialog::ShowModal (this=<value optimized out>) at ./src/gtk/dialog.cpp:146
#21 0x0000003b39b017ed in wxGetSingleChoiceIndex (message=<value optimized out>, caption=<value optimized out>, n=<value optimized out>, choices=<value optimized out>, parent=<value optimized out>) at ./src/generic/choicdgg.cpp:127
#22 0x0000003b39b01915 in wxGetSingleChoiceIndex (message=<value optimized out>, caption=<value optimized out>, aChoices=<value optimized out>, parent=<value optimized out>, x=<value optimized out>, y=<value optimized out>, centre=<value optimized out>, width=Could not find the frame base for "wxGetSingleChoiceIndex(wxString const&, wxString const&, wxArrayString const&, wxWindow*, int, int, bool, int, int)".
)
    at ./src/generic/choicdgg.cpp:146
#23 0x00002aaab3bb6755 in CodeCompletion::OnGotoDeclaration (this=0xcd5e5a0, event=...) at codecompletion.cpp:2863
#24 0x0000003744cfcbff in wxEvtHandler::ProcessEventIfMatches (entry=<value optimized out>, handler=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1239
#25 0x0000003744cfcd9f in wxEventHashTable::HandleEvent (this=<value optimized out>, event=<value optimized out>, self=<value optimized out>) at ./src/common/event.cpp:906
#26 0x0000003744cfcee9 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1301
#27 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#28 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#29 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#30 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#31 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#32 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#33 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#34 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#35 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#36 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#37 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#38 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#39 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#40 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#41 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#42 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#43 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#44 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#45 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#46 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#47 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#48 0x0000003b39af8b46 in wxWindowBase::TryParent (this=<value optimized out>, event=<value optimized out>) at ./src/common/wincmn.cpp:2661
#49 0x0000003744cfce90 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1314
#50 0x0000003744cfce80 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1308
#51 0x0000003b39af8b46 in wxWindowBase::TryParent (this=<value optimized out>, event=<value optimized out>) at ./src/common/wincmn.cpp:2661
#52 0x0000003744cfce90 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1314
#53 0x0000003b39af8b46 in wxWindowBase::TryParent (this=<value optimized out>, event=<value optimized out>) at ./src/common/wincmn.cpp:2661
#54 0x0000003744cfce90 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1314
#55 0x00002aaab6f70ced in wxMenuCmd::Exec (this=0xdd1ee60, origin=0xdd5bc70, client=0xdd5bc70) at menuutils.cpp:543
#56 0x00002aaab6f63b11 in wxKeyBinder::OnChar (this=0xdcfd320, event=..., next=0xdd5bc70) at keybinder.cpp:1429
#57 0x00002aaab6f63c3b in wxBinderEvtHandler::OnChar (this=0xdd5c730, p=...) at keybinder.cpp:791
#58 0x0000003744cfcbff in wxEvtHandler::ProcessEventIfMatches (entry=<value optimized out>, handler=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1239
#59 0x0000003744cfcd9f in wxEventHashTable::HandleEvent (this=<value optimized out>, event=<value optimized out>, self=<value optimized out>) at ./src/common/event.cpp:906
#60 0x0000003744cfcee9 in wxEvtHandler::ProcessEvent (this=<value optimized out>, event=<value optimized out>) at ./src/common/event.cpp:1301
#61 0x0000003b399f8ef6 in gtk_window_key_press_callback (widget=<value optimized out>, gdk_event=<value optimized out>, win=<value optimized out>) at ./src/gtk/window.cpp:1034
#62 0x0000003b3872ffcd in ?? () from /usr/lib64/libgtk-x11-2.0.so.0
#63 0x000000373f60b08a in g_closure_invoke () from /lib64/libgobject-2.0.so.0
#64 0x000000373f61b2ed in ?? () from /lib64/libgobject-2.0.so.0

BTW the std::set crash is not fixed, but now it is very rare. Debuggers branch latest revision on Centos Amd64 linux.
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Is CC crash, or Debugger plugin?
« Reply #74 on: August 23, 2011, 11:26:35 am »
Pressing ctrl+shift+. is very deadlocky operation, it happened twice already today. Latest version of debugger's branch.
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]
Pages: 1 2 3 4 [5] 6 7 8   Go Up
« previous next »