<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi,<br>
</p>
<div class="moz-cite-prefix">Στις 10/2/2021 2:25 μ.μ., ο/η Christo
Crause έγραψε:<br>
</div>
<blockquote type="cite"
cite="mid:CAGOmfbGy=O51HiVBfJPozooO_H1CHnONH4R6-=8sh5EXdYjkHw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Wed, Feb 10, 2021 at 12:47 PM Dimitrios Chr.
Ioannidis via fpc-devel <<a
href="mailto:fpc-devel@lists.freepascal.org"
moz-do-not-send="true">fpc-devel@lists.freepascal.org</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I read at compiler/systems/i_embed.pas the AVR
systeminfo, is the <br>
only one that, has as default "dbg : dbg_dwarf3". The other
embed <br>
systems that uses dwarf ( ARM, MIPSEL, i8086, m68k,
RISCV32/64, XTENSA, <br>
Z80 ), all have as default "dbg : dbg_dwarf2".<br>
<br>
The AVR has problems with dbg_dwarf2 ? If not, could you
please <br>
change the AVR systeminfo to dwarf2 also for consistency ?<br>
</blockquote>
<div><br>
</div>
<div>That was a fix for compiling controller units with lots
of symbols, refer to this discussion thread: <a
href="https://www.mail-archive.com/fpc-devel@lists.freepascal.org/msg35416.html"
moz-do-not-send="true">https://www.mail-archive.com/fpc-devel@lists.freepascal.org/msg35416.html</a></div>
<div>Dwarf2 is fine in general, unless the address (I think
address in dwarf debug section, the details are a bit hazy
in my memory) of symbols exceed 65535. Dwarf3 offers a
larger data type for this scenario.</div>
</div>
</div>
</blockquote>
<p> I'm using ppcrossavr with systeminfo default "dbg : dbg_dwarf2"
with no problems. If I remember correctly, IMHO, fixing the issue
33914 ( <a class="moz-txt-link-freetext" href="https://bugs.freepascal.org/view.php?id=33914">https://bugs.freepascal.org/view.php?id=33914</a> ) had the
collateral effect to fixing also the above.</p>
<p> For test, I just debugged a physical atmega32u2 mcu with Lazarus
with no problems at all. Also for test, I builded an avr35 subarch
ppcrossavr and also debugged a physical atmega32u2 mcu with no
problems.</p>
<p>ppcrossavr ( from trunk ) builded on Windows 10 x64 ( with avr
binutils 2.34 from <a class="moz-txt-link-freetext"
href="https://blog.zakkemble.net/avr-gcc-builds/">https://blog.zakkemble.net/avr-gcc-builds/</a>
) :</p>
<p>make.exe clean crossall crossinstall CPU_TARGET=avr
OS_TARGET=embedded SUBARCH=avr35
INSTALL_PREFIX=G:\Programming\dimitris\tools\<br>
fpc-trunk CROSSOPT="-g -godwarfsets -gw2 -O1 -dDEBUG"
CROSSBINDIR=G:\Programming\dimitris\tools\fpc-trunk\bin\x86_64-win64
BINUTILSPREFIX=avr-embedded-</p>
<p>regards,</p>
<p>-- <br>
</p>
<p>Dimitrios Chr. Ioannidis<br>
</p>
</body>
</html>