[Lazarus] Cannot debug app (gdb errors)

Leonardo M. Ramé l.rame at griensu.com
Sat Nov 10 15:14:42 CET 2012


On 2012-11-10 14:16:11 +0100, Martin wrote:
> On 10/11/2012 11:58, Leonardo M. Ramé wrote:
> >On 2012-11-09 10:11:36 -0300, Leonardo M. Ramé wrote:
> >>My locale and LC_Type are es_AR.
> >>
> >>Here's the content of the debug window:
> >>
> >>=thread-group-added,id="i1"
> >>(gdb)
> >><-gdb-set confirm off>
> >Well, let's start again.
> >
> >I've built gdb 7.5 and 7.3.1 from sources, and used those instead of the
> >one installed by default in Ubuntu, but the problem persists.
> >
> >I've updated Lazarus and FPC from svn trunk and compiled them, the
> >problem is still there.
> >
> 
> 
> 
>  << TCmdLineDebugger.ReadLn "&"buildsym.c:701: internal-error: la
> verificaci\303\263n de consistencia interna fall\303\263\nA problem
> internal to GDB has been detected,\nfurther debugging may prove
> unreliable.""
>   << TCmdLineDebugger.ReadLn "&"\n""
>   << TCmdLineDebugger.ReadLn ""
> 
> You current problem is not related to the GDB locale.
> 
> GDB crashes while reading the debug info (dwarf or stabs, whatever
> you used / maybe even mixed).
> 
> This problem exists in all GDB versions that I know.
> 
> I can not tell if it is a GDB (it should be an error not a crash)
> only issue, or part FPC or linker (maybe there is invalid encoding,
> maybe not...)
> 
> This means it can not be fixed in Lazarus. Once it is known which
> part in the info is causing the crash, it can either be avoided by
> FPC (unless it is the linker) or needs to be fixed in GDB.
> 

I must also add the problem only exists when trying to run a specific
application, even without debugging info, with others the debugger runs ok.

-- 
Leonardo M. Ramé
http://leonardorame.blogspot.com




More information about the Lazarus mailing list