User forums > Help

using code profiler in C - crash! (svn 7071)

<< < (3/5) > >>

wangdong1226:
Dear oBFusCATed,

Sadly, this patch can not work when code profiler in C language. (code profiler works for C++ language as before).

 :(

I've installed new released wxWidgets 2.8.12 (wxGTK-2.8.12, wxBase-2.8.12, wx......)  in my Fedora 14 x86_64 system.

oBFusCATed:
This is not a code profiler patch!
It should fix the compilation of the code snippets plugin, when wxGTK is installed from the official package in Fedora/CentoOS.
Is this the case?

Anyone against this patch? Pecan?

wangdong1226:

--- Quote from: oBFusCATed on March 29, 2011, 04:41:07 pm ---This is not a code profiler patch!
It should fix the compilation of the code snippets plugin, when wxGTK is installed from the official package in Fedora/CentoOS.
Is this the case?

Anyone against this patch? Pecan?

--- End quote ---

OK, I'll test it again and submit the report then.

BTW, if I want to use official released wxWidgets 2.8.12, how to fix the code profiler problem when used in C language ?  (in C++, code profiler works well).
Any suggestion or solution?


Best regards.
David.

Pecan:

--- Quote from: oBFusCATed on March 29, 2011, 04:41:07 pm ---This is not a code profiler patch!
It should fix the compilation of the code snippets plugin, when wxGTK is installed from the official package in Fedora/CentoOS.
Is this the case?

Anyone against this patch? Pecan?

--- End quote ---

I don't understand how assigning 0 to a variable causes this problem.
There are a number of tests in the code to see if m_itemAtKeyDown and m_itemAtKeyUp are empty. Simply removing initialization of the variables is a dangerous answer.
Can they guarantee that the assignment of an empty wxTreeItemId() is going to be 0 for all variations and flavors of wxWidgets?

Could someone please show us the error message.

stahta01:
@Pecan:

I have already told wangdong1226 that wxWidgets can NOT be compiled with 2.4 compatible option on 64 bit system.
To reproduce the issue, I would guess you have to do what wangdong1226 did and use the Fedora RPM that has WXWIN_COMPATIBILITY_2_4 set to 1 in setup.h

Tim S.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version