Re: [Lazarus] GDB output warnings of internal errors
Hi Martin, On 2015-06-29 12:48, Martin Frb wrote: > And > ensure *all* packages (that is all packages that have debug info) have > the same stabs or dwarf setting. That seems to have been the cause of GDB crashing. The lazarus packages fpspreadsheet had hard-coded "Stabs" debugging, but the rest of my project had "Automatic" which I believe it then results to "Dwarf" under Linux. Thanks for that tip! Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] GDB output warnings of internal errors
On 29/06/2015 09:59, Graeme Geldenhuys wrote: Hi, Is the following "internal errors" normal output for GDB? I'm using FreeBSD 10.1 64-bit with GDB v7.81 ... (gdb) <-exec-continue> &"warning: (Internal error: pc 0x58df30 in read in psymtab, but not in symtab.)\n" &"\n" ^running *running,thread-id="all" (gdb) =library-loaded,id="/usr/lib/i18n/libiconv_std.so.4",target-name="/usr/lib/i18n/libiconv_std.so.4",host-name="/usr/lib/i18n/libiconv_std.so.4",symbols-loaded="0",thread-group="i1" &"warning: (Internal error: pc 0x59f588 in read in psymtab, but not in symtab.)\n" No idea if they are "normal". But since many of them happen during library loading, I would try the following setting: http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#gdb.exe_has_stopped_working This will tell gdb to ignore libraries. If it happens outside of libraries too, then try stabs vs dwarf. And ensure *all* packages (that is all packages that have debug info) have the same stabs or dwarf setting. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] GDB output warnings of internal errors
Hi, Is the following "internal errors" normal output for GDB? I'm using FreeBSD 10.1 64-bit with GDB v7.81 Lazarus 1.5 r49362 FPC 2.6.4 x86_64-freebsd-gtk 2 I see pages and pages of these warnings when I start my application up. The reason I ask, is because yet again I can't debug my application. As soon as it is supposed to hit a breakpoint, GDB seems to crash I all I can do is click the "stop debugging" button. I don't know if these warnings have anything todo with it. The fpdebug alternative option also seems to crash as soon as it is supposed to hit the breakpoint. (gdb) <-exec-continue> &"warning: (Internal error: pc 0x58df30 in read in psymtab, but not in symtab.)\n" &"\n" ^running *running,thread-id="all" (gdb) =library-loaded,id="/usr/lib/i18n/libiconv_std.so.4",target-name="/usr/lib/i18n/libiconv_std.so.4",host-name="/usr/lib/i18n/libiconv_std.so.4",symbols-loaded="0",thread-group="i1" &"warning: (Internal error: pc 0x59f588 in read in psymtab, but not in symtab.)\n" &"\n" &"warning: (Internal error: pc 0x5a34d0 in read in psymtab, but not in symtab.)\n" &"\n" &"warning: (Internal error: pc 0x5a35f0 in read in psymtab, but not in symtab.)\n" &"\n" =library-loaded,id="/usr/lib/i18n/libUTF8.so.4",target-name="/usr/lib/i18n/libUTF8.so.4",host-name="/usr/lib/i18n/libUTF8.so.4",symbols-loaded="0",thread-group="i1" &"warning: (Internal error: pc 0x59f588 in read in psymtab, but not in symtab.)\n" &"\n" &"warning: (Internal error: pc 0x5a34d0 in read in psymtab, but not in symtab.)\n" &"\n" &"warning: (Internal error: pc 0x5a35f0 in read in psymtab, but not in symtab.)\n" Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
