Help in debugging crash

Do you have a typical platform dependent issue you're battling with ? Ask it here. Make sure you mention your platform, compiler, and wxWidgets version.
Post Reply
gm
In need of some credit
In need of some credit
Posts: 2
Joined: Tue Jan 15, 2019 10:09 pm

Help in debugging crash

Post by gm » Wed Jan 16, 2019 6:52 am

I am trying to debug crash
https://github.com/BOINC/boinc/issues/2350

and I compiled BOINC with "-Og" flag, and runned it with
GDK_SYNCHRONIZE=1 boincmgr
command.

BOINC crashes in the rapid switch from simple view to advanced view, in particular the lastest BOINC functions called are


NoticeListCtrl.cpp line 70:

CNoticeListCtrl::CNoticeListCtrl( wxWindow* parent ) {
Create( parent );
}

that is called from ViewNotices.cpp line 70:

m_pHtmlListPane = new CNoticeListCtrl(this);

then you start to go through the various libraries, to end with
check = node && node->is_instantiatable && iface && type_node_conforms_to_U (node, iface, TRUE, FALSE);
from gtype.c file.

I made the backtrace from that function to the lastest BOINC functions called, but I cannot manage to find where is the problem. Do you have any suggestions for me to better investigate?

Hereunder I attach the complete GDB backtrace and stderrgui output

Thank you

User avatar
doublemax
Moderator
Moderator
Posts: 13870
Joined: Fri Apr 21, 2006 8:03 pm
Location: $FCE2

Re: Help in debugging crash

Post by doublemax » Wed Jan 16, 2019 8:52 am

We can't help debug complex applications for you. If you think this is caused by a bug in wxWidgets, please create a small compilable sample that demonstrates the issue.
Use the source, Luke!

ONEEYEMAN
Part Of The Furniture
Part Of The Furniture
Posts: 3352
Joined: Sat Apr 16, 2005 7:22 am
Location: USA, Ukraine

Re: Help in debugging crash

Post by ONEEYEMAN » Wed Jan 16, 2019 3:22 pm

Hi,
You should run the program under gdb and get the backtrace at the time of the crash.
Then look at the last call from your program and see what might be the issue.

If you are not familiar with gdb - you should get one of the tutorial on the web.

Thank you.

gm
In need of some credit
In need of some credit
Posts: 2
Joined: Tue Jan 15, 2019 10:09 pm

Re: Help in debugging crash

Post by gm » Wed Jan 16, 2019 7:59 pm

ONEEYEMAN wrote:Hi,
You should run the program under gdb and get the backtrace at the time of the crash.
Hi, I already did that and I attached it in the first post (quoted hereunder)
gm wrote: Hereunder I attach the complete GDB backtrace and stderrgui output
doublemax wrote:We can't help debug complex applications for you. If you think this is caused by a bug in wxWidgets, please create a small compilable sample that demonstrates the issue.
Which Linux distribution do you use? So that I can better provide a working example

ONEEYEMAN
Part Of The Furniture
Part Of The Furniture
Posts: 3352
Joined: Sat Apr 16, 2005 7:22 am
Location: USA, Ukraine

Re: Help in debugging crash

Post by ONEEYEMAN » Wed Jan 16, 2019 9:32 pm

Hi,
doublemax, does not work under Linux - Windows only. ;-)
But as I said - you should analyze the backtrace and see what might go wrong. Start with the line in the backtrace that refer to the program you are debugging and see what is causing the crash.

Hint: Most likely reason it is a NULL pointer...

Thank you.

Post Reply