View Single Post
  #2   (View Single Post)  
Old 29th April 2013
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,977
Default

Quote:
Anyone got any ideas what could be wrong?
The answers will be in the .core file saved in your working directory upon application failure.

Bad news: the .core file will not have any debugging symbols within, so will be nearly useless for diagnostics.

Good news: you can reproduce the problem at will. All you need now is a executable with debugging symbols for diagnostics.

You would have to:
  1. Install the ports tree for 5.2 or 5.2-stable.
  2. Build the port with debugging symbols enabled and replace the installed package with the newly created package.
  3. Recreate a .core file with the new executable(s).
  4. Debug with gdb(1).
Note that this is the minimum set of steps required. If the error is occurring within a shared library, you'll have to rebuild the shared library with debugging symbols also. Luckily, the .core file you have now will at least tell you which module is failing, and from that, you will be able to determine if a shared library is involved. See the gdb(1) man page.



Whether or not you want to go through these steps is entirely up to you, of course.
Reply With Quote