Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2006-03

debugging probelm

3 messages · 2 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Unknown author

Hi!

In Lazarus.when I debug a file. That is , the debugger stops and I look at the call stack, I cannot see filename and linenumber.... In other words, the debugging is made harder.
I heard it was related to the freepascal compiler was not able to cooperate with gdb as the generated stack frame format changed... What is the timeframe in which this problem may be fixed? What debugger do you use that does not have this problem?

Thanks...

Márton Papp

Reply by email

Peter Vreman
to Unknown author
Show quoted text 9 lines
Hi! In Lazarus.when I debug a file. That is , the debugger stops and I look at the call stack, I cannot see filename and linenumber.... In other words, the debugging is made harder. I heard it was related to the freepascal compiler was not able to cooperate with gdb as the generated stack frame format changed... What is the timeframe in which this problem may be fixed? What debugger do you use that does not have this problem?

You forget to mention all important information like which os and cpu, commandline options and compiler version you are using.

If you want timelines for fixes on the debugger gdb itself ask the binutils mailinglists.

Reply by email

Unknown author
to Peter Vreman
Peter Vreman wrote 17 lines
> Hi! > > In Lazarus.when I debug a file. That is , the debugger stops and I look > at the call stack, I cannot see filename and linenumber.... > In other words, the debugging is made harder. > I heard it was related to the freepascal compiler was not able to > cooperate with gdb as the generated stack frame format changed... > What is the timeframe in which this problem may be fixed? > What debugger do you use that does not have this problem? > You forget to mention all important information like which os and cpu, commandline options and compiler version you are using. If you want timelines for fixes on the debugger gdb itself ask the binutils mailinglists.

I wonder if you know about this as this issue you could have met or can be interested in.

Show quoted text 8 lines
_______________________________________________ fpc-devel maillist - http://lists.freepascal.org/mailman/listinfo/fpc-devel

Ok.
WinXp. Free Pascal Compiler version 2.1.1 [2006/03/08] for i386. I use the compiler in Lazarus.
The compiler output:
TCompiler.Compile WorkingDir="C:\lazarus\dynhasharray\" CompilerFilename="C:\laz
arus\pp\bin\i386-win32\ppc386.exe" CompilerParams=" -S2cgi -g -gl -vewnhi -l -Fu
C:\lazarus\lcl\units\i386-win32\ -Fu.
-oC:\lazarus\dynhasharray\dynhasharraytest
.exe dynhasharraytest.lpr"
[TCompiler.Compile] CmdLine="C:\lazarus\pp\bin\i386-win32\ppc386.exe -S2cgi -g
-gl -vewnhi -l -FuC:\lazarus\lcl\units\i386-win32\ -Fu. -oC:\lazarus\dynhasharra
y\dynhasharraytest.exe dynhasharraytest.lpr"

Márton Papp

Reply by email