Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Crash using copy and paste (reproducable)
Pecan:
--- Quote from: Biplab on February 12, 2007, 11:15:28 am ---This is bugging me too. I'm using C::B Revison 3593, OpenSUSE 10.2, wxGTK-2.6.3.1 and wx is compiled as Release-Dynamic-Unicode-Monolithic.
--- End quote ---
@Biplab
C::B crashes after using Ctrl+V or Edit>Paste.
Since you're getting this crash, could you trap it and give us a backtrace.
You can use the follow (or like) bash shell to trap the crash.
--- Code: ---#!/bin/sh
echo run>run.txt
APP_DIR=`pwd`
export LD_LIBRARY_PATH=$APP_DIR:$LD_LIBRARY_PATH
gdb --command=run.txt --args $APP_DIR/codeblocks $@
--- End code ---
If you're using windows, just run codeblocks under gdb, like
gdb codeblocks
run
You can make a .cmd file for it like:
--- Code: ---echo run>run.txt
gdb -command=run.txt codeblocks
--- End code ---
Biplab:
--- Quote from: Pecan on February 12, 2007, 03:03:09 pm ---
--- Quote from: Biplab on February 12, 2007, 11:15:28 am ---This is bugging me too. I'm using C::B Revison 3593, OpenSUSE 10.2, wxGTK-2.6.3.1 and wx is compiled as Release-Dynamic-Unicode-Monolithic.
--- End quote ---
@Biplab
C::B crashes after using Ctrl+V or Edit>Paste.
Since you're getting this crash, could you trap it and give us a backtrace.
You can use the follow (or like) bash shell to trap the crash.
--- Code: ---#!/bin/sh
echo run>run.txt
APP_DIR=`pwd`
export LD_LIBRARY_PATH=$APP_DIR:$LD_LIBRARY_PATH
gdb --command=run.txt --args $APP_DIR/codeblocks $@
--- End code ---
--- End quote ---
Thanks a lot for the detailed instruction. :D I'm not familiar with GDB and they will help me a lot.
I'll post it after some time. (Currently I'm in Windows and compiling GCC-3.4.6. It's not over yet. :))
By the way do I need to run it from src/devel dir or I can run it from /usr/local/bin dir ?
fleuba:
Hi again,
Sorry you guys if my post looked a bit upseting. I'm just so fed up with this bug, but in the meanwhile I know developping such a big and great software is a lot of work.
This bug seems to occure only for a few people, so it is tempting to move it very far in the todo list.
Nevertheless, thank you for the answer. I'll reproduce the bug and provide you with the crash stack today.
I hope this will help you to fix it... I can cooperate even more as you need.
Fred
Pecan:
@Biplab:
When in wndows, run it from the src/devel.
When in Linux run it from where the codeblocks executable is.
Else just change the APP_DIR=`pwd` to the dir of codeblocks, and run it from anywhere.
For example, here's one without gdb running the nightly install (not my compiled svn install) from /home/pecan/cbNightly/usr/bin with the LIB also changed.
I cd to /home/pecan/cbNightly/usr/bin and issue ./run.sh
--- Code: ---#!/bin/sh
APP_DIR=`pwd`
export LD_LIBRARY_PATH=$APP_DIR/lib:$LD_LIBRARY_PATH
$APP_DIR/bin/codeblocks --prefix=$APP_DIR $@
--- End code ---
When the crash finally occurs, issue the command:
bt full
and keep hitting enter (not quit) until the backtrace finishes with a (gdb) prompt.
copy and paste to taste. I like to open an external editor and paste the whole monte so I can restart CB and read the trace later.
Pecan:
Here's a nice 2 page quick reference for GDB.
http://www.cs.dal.ca/studentservices/refcards/gdbref.pdf
KeyWords: GDB Quick Reference
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version