C::B svn rev 1780 linux build

[tiwag]

@Yiannis,

in rev1780 you made some changes in sdk/editorconfigurationdlg.cpp which leads to the following warning when building under linux:

g++ -Wall -g `wx-config --cflags` -fmessage-length=0 -fexceptions -Winvalid-pch -DcbDEBUG -DCB_PRECOMP  -Isdk/wxscintilla/include -Isdk -Isdk/as/source -Isdk/as/include -Isdk/propgrid/include -Isdk/wxFlatNotebook -I/usr/include  -c sdk/editorconfigurationdlg.cpp -o .objs/sdk/editorconfigurationdlg.o
In file included from sdk/editorconfigurationdlg.cpp:26:
sdk/sdk_precomp.h:10:18: warning: sdk/sdk.h.gch: settings for -fexceptions do not match
sdk/editorconfigurationdlg.cpp:477:3: warning: #warning "wxComboBox::SetString() doesn't work under non-win32 platforms"

[mandrav]

This is there a long time....
Oh, and I recommend you delete sdk/sdk.h.gch. It will be recreated with the correct settings and PCH will work for you again

[tiwag]

it would be fine, if the compiler options would be identical for using autotools and codeblocks-project file in order not to get some pch related warnings.

at the moment i have some problems with crashing codeblocks under linux, when i want to open any editor !
that's the reason, why i switched back to the autotools version, in order to see if it works ok with the autotools generated version - but it crashes too ! the precompiled headers weren't re-generated since this last build.
normally i work with the src/output/codeblocks version to build the src/devel/codeblocks.

do you have these crashes too , when opening an editor ?
this worked fine for me until approx. svn rev 1750

thx,
--tiwag

[tiwag]

@Yiannis, don't worry !

i traced it back and found that linux-CB crashes only when using the keybinder plugin,
when you're going to open any file which belongs to the project.

maybe pecan will find this useful
(gdb) run
Starting program: /home/tiwag/Devel/CodeBlocks/trunk/src/devel/codeblocks
[Thread debugging using libthread_db enabled]
[New Thread -1228863808 (LWP 10912)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1228863808 (LWP 10912)]
0xb7c2f40a in wxMenuItemBase::GetLabelFromText () from /usr/lib/libwx_gtk2u_core-2.6.so.0
(gdb) bt
#0  0xb7c2f40a in wxMenuItemBase::GetLabelFromText () from /usr/lib/libwx_gtk2u_core-2.6.so.0
#1  0xb65c7c2b in wxMenuItemBase::GetLabel (this=0x8568418) at menuitem.h:68
#2  0xb65c68c0 in wxMenuCmd::Update (this=0x8394468) at menuutils.cpp:79
#3  0xb65c5846 in wxKeyBinder::UpdateAllCmd (this=0x841ff80) at keybinder.h:709
#4  0xb65bc9d7 in wxKeyBinder::Attach (this=0x841ff80, p=0x8b17358) at keybinder.cpp:831
#5  0xb65b7d04 in cbKeyBinder::OnEditorOpen (this=0x90ae318, event=@0xbf861444) at cbkeybinder.cpp:701
...

[tiwag]

but i have another problem with the recent linux CB svn build .

during debugging, i don't have any information in the editor,
where the debugger has actually stopped.

in the Debugger messages tab the "At filename:linenumber" is displayed,
but the editor information is not updated.
(in windows builds we have a small triangle indicating the actually stopped source code line)

[mandrav]

I will look at this debugging issue later this afternoon.

[Pecan]

@Yiannis, don't worry !

i traced it back and found that linux-CB crashes only when using the keybinder plugin,
when you're going to open any file which belongs to the project.

maybe pecan will find this useful

Thankyou tiwag

yes, I know the problem. It happened when I re-instated
the original GTK code (separating out the WXMSW code).

It happens when a menuitem disappears/reappears.

I didn't want to screw with that code again until I had
a linux to test on. But you *know* how that went.

I'll fix this as soon as I can figure out how to make
CB compile under linux.

thanks
pecan

[tiwag]

I will look at this debugging issue later ...

thx Yiannis - CB rev 1816 ubuntu linux build is debugging fine now !!!