Recent

Author Topic: Testers wanted: FpDebug on Linux and Windows  (Read 4692 times)

ccrause

  • Sr. Member
  • ****
  • Posts: 331
Re: Testers wanted: FpDebug on Linux and Windows
« Reply #30 on: December 04, 2020, 02:14:25 pm »
In trunk, a 64bit IDE can debug a 32bit target.
I thought so. Unfortunately my employer supplied Windows machine has a policy that prevents copying anything containing "vlc", so getting FPC or Lazarus trunk sources on it is a major pain.  The only way I managed is to use an installer, which then skip the vlc packages on error.

Quote
And indeed it gives no error, so that part should be reported on mantis.
Issue 38167

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 6825
  • Debugger - SynEdit - and more
    • wiki
Re: Testers wanted: FpDebug on Linux and Windows
« Reply #31 on: December 04, 2020, 04:20:22 pm »
and every subsequent user of this demo will have to use dwarf debug info.

Well, DWARF is the way better debug info. And for some targets FPC even does no longer has stabs.

In fact I had plans for a long time to change the IDE default. But that involves the Makefiles....

wp

  • Hero Member
  • *****
  • Posts: 7977
Re: Testers wanted: FpDebug on Linux and Windows
« Reply #32 on: December 07, 2020, 07:07:14 pm »
Is there a way to avoid changing the project settings when FPDebug is used, or to write the changed settings to the session file rather than to the lpi file?

Afaik, debug info is stored in session.

I opened one of the examples to check, and
  Project options > Session
showed
  "Save in lpi file"

IMHO, that should be set to "save in lps" for all examples.
That would then need to be committed once to svn.

I prefer lps in project dir, but if you want clean svn checkouts, then it needs to be in config dir (which afaik can lead to name clashes)

I've got to return to this topic... In the attachment there is a simple project which just does what I described above: it stores debug settings in the lpi file although "Project options" > "Session" shows "Save in lps file in current directory". This is a standard gui project with some controls and a stupid calculation created from default parameters. Since the debugger in my system is fpdebug I was forced to select one of the dwarf debug settings upon compilation. Looking into the lpi file I see that it contains this information. Martin, according to your response I would expect it to be in the lps file:

Code: XML  [Select][+][-]
  1.     <Linking>
  2.       <Debugging>
  3.         <DebugInfoType Value="dsDwarf2"/>
  4.       </Debugging>
  5.       <Options>
  6.         <Win32>
  7.           <GraphicApplication Value="True"/>
  8.         </Win32>
  9.       </Options>
  10.     </Linking>

Am I missing some setting to avoid this? And what is different in the Lazarus example projects?

I am using Laz trunk on Win10.
Mainly Lazarus trunk / fpc 3.2.0 / all 32-bit on Win-10, but many more...

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 6825
  • Debugger - SynEdit - and more
    • wiki
Re: Testers wanted: FpDebug on Linux and Windows
« Reply #33 on: December 07, 2020, 08:37:42 pm »
Please report it as bug then.  This pre-dates fpdebug.

I assumed it to always have been session.

Sieben

  • Full Member
  • ***
  • Posts: 196
Re: Testers wanted: FpDebug on Linux and Windows
« Reply #34 on: December 07, 2020, 08:51:12 pm »
Just yesterday I happened to notice that some of my packages contain this info as well in their .lpk-files. And that these settings obviously override the general setting for rebuilding IDE ('-gw3'). Packages that do not include explicit debug settings with their .lpk-file are listed with 'Automatic (-g)' in the IDE and also compile without info for fpdebug.

Edit: forgot to mention that fpdebug works great for me as well. I wouldn't go back to gdb even if these problems were solved.
« Last Edit: December 07, 2020, 09:31:23 pm by Sieben »
Lazarus 2.0.10, FPC 3.2.0, .deb install on Ubuntu Xenial 32 / Gtk2 / Unity7

 

TinyPortal © 2005-2018