It usually results when a program accesses memory outside it's allocated space. Or maybe the program tries to access a resource at a particular memory location, but the resource isn't there. It can be a real pain tracking down the offending line/lines of code.

I think to use an binary with gdb you need to compile it with the debug info set.

Quote:

Before you can get started, the program you want to debug has to be compiled with debugging information in it. This is so gdb can work out the variables, lines and functions being used. To do this, compile your program under gcc (or g++) with an extra '-g' option:

gcc -g eg.c -o eg

If you wanted to try a gui frontend for gdb, I've uploaded a .pet of ddd in this thread. (Wouldn't it be ironic if ddd didn't work as well!).

There's also a tcl based gdb frontend called insight. Being tcl-based it's quite easy to get going...at least on pre-4 pups.

Thanks muggins, but ddd PET doesn't work on Puppy4. Something wrong with dependencies. Might try to make it work later, or even compile it, but now I'll just have to stick with commandline gdb.
EDIT: tried to compile ddd on Puppy4 - got an error:

Quote:

In file included from /usr/include/Xm/XmP.h:1646,
from ScrolleGEP.h:37,
from ScrolledGE.C:33:
/usr/include/X11/VendorP.h:87: error: previous declaration of 'VendorShellClassRec vendorShellClassRec' with 'C++' linkage
/usr/include/Xm/VendorSP.h:58: error: conflicts with new declaration with 'C' linkage
make[2]: *** [ScrolledGE.o] Error 1

Lesstif compiled without problems.
Whole conversation got out of topic, maybe it's time for move?Last edited by Joshas on Mon 12 May 2008, 08:40; edited 1 time in total

I'm after searchmonkey, unless there's another file search application with "classic" interface and minimal set of dependencies. findwild is an interesting program, but the GUI is too weird. Another must is an ability to localize UI.

UPDATE: after compiling Insight (it took some time, and result weighs 50MB) I finally managed to get searchmonkey running - no more segmentation faults. To fix it, I just commented out two lines in interface.c source code:
1271: gtk_text_view_set_overwrite (GTK_TEXT_VIEW (textview1), TRUE);
1300: gtk_text_view_set_overwrite (GTK_TEXT_VIEW (textview4), TRUE);
I'm not sure what is wrong with theese lines (might need to check out GTK docs), and I have no idea how to fix it properly, so any help is welcome.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum