User forums > Embedded development
C::B crashes when I try to a big data structure by moving pointer on it.
stahta01:
I strongly suggest using wxWidgets 2.8 instead of the development version 2.9.
IIRC, 2.8.10 is the normal version of wxWidgets being used.
Tim S.
Kaijun:
--- Quote from: stahta01 on February 25, 2011, 02:22:18 am ---I strongly suggest using wxWidgets 2.8 instead of the development version 2.9.
IIRC, 2.8.10 is the normal version of wxWidgets being used.
Tim S.
--- End quote ---
Thanks! I got it work on wxWidgets 2.8.11. But it still crashes. I got errors from xterm,
Gdk-ERROR **: The program 'codeblocks' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 782010 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
When debugging, another issue is that some source files in the stack window display the paths under the project dir. But they are in different paths. They are compiled into shared libs. What is interesting is other files which are compiled into the static libs, then into the shared libs can show absolute paths, That makes impossible to open these files from the stack.
oBFusCATed:
Can you provide a sample project, which crashes C::B?
--- Quote from: Kaijun on February 25, 2011, 02:43:35 pm ---When debugging, another issue is that some source files in the stack window display the paths under the project dir. But they are in different paths. They are compiled into shared libs. What is interesting is other files which are compiled into the static libs, then into the shared libs can show absolute paths, That makes impossible to open these files from the stack.
--- End quote ---
A sample project will be helpful, too.
Kaijun:
--- Quote from: oBFusCATed on February 25, 2011, 02:54:42 pm ---Can you provide a sample project, which crashes C::B?
--- Quote from: Kaijun on February 25, 2011, 02:43:35 pm ---When debugging, another issue is that some source files in the stack window display the paths under the project dir. But they are in different paths. They are compiled into shared libs. What is interesting is other files which are compiled into the static libs, then into the shared libs can show absolute paths, That makes impossible to open these files from the stack.
--- End quote ---
A sample project will be helpful, too.
--- End quote ---
I debug on omap3530. You can try mplayer or ffmpeg in linux on PC. There are some big data structures in codecs in ffmpeg. They are available from http://www.mplayerhq.hu/design7/dload.html.
oBFusCATed:
No, no big projects, the bug can be reproduce with simple sample...
You can make the sample by copying the data structure causing the crashes in a single source file and populating it with data to make C::B crash.
Making the sample increases the chances for fixing the bug, else you should wait me to encounter it, so I have a way to reproduce it. :lol:
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version