From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: debuginfo Dwarf Error
Date: Tue, 04 Jul 2017 21:17:00 -0000 [thread overview]
Message-ID: <9acd520b-b080-2938-1e12-b61280f33a3f@gmail.com> (raw)
In-Reply-To: <2fdd2634-64d4-d5d0-045c-8e3497a1bf6f@gmail.com>
On 03/07/2017 17:41, Marco Atzeri wrote:
> On 03/07/2017 15:31, JonY wrote:
>> On 07/03/2017 10:22 AM, Marco Atzeri wrote:
>>> On 02/07/2017 11:53, JonY wrote:
>>>> On 07/02/2017 06:22 AM, Marco Atzeri wrote:
>>>>> Hi,
>>>>> while extracting debuginfo on 32 bit gdal dll
>>>>>
>>>>> $ ls -s cyggdal-20.dll
>>>>> 103M cyggdal-20.dll
>
>
>>
>> I don't really have anything else to suggest, how big is the dll anyway
>> (how many exports, how many bytes is size)?
>
> 103 MBbytes.
>
> As the issue is only on 32bit and not on 64bit,
> it could be a counter limitation
>
> I am trying to test again with gcc 6.3.0-2
>
> Thanks
> Marco
>
Jon,
I noted that the problem was already present sometime ago
https://cygwin.com/ml/cygwin/2015-10/msg00122.html
and supposed to be solved.
However it seems arisen again
$ cat getcwd.c
#include <limits.h>
#include <unistd.h>
int
main ()
{
char buf[PATH_MAX];
getcwd (buf, PATH_MAX);
}
$ gcc getcwd.c
$ nm -l a.exe
nm: Dwarf Error: Could not find abbrev number 85.
....
Using latest test versions make no difference
$ cygcheck -c gcc-core binutils
Cygwin Package Information
Package Version Status
binutils 2.28-2 OK
gcc-core 6.3.0-2 OK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-07-04 21:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 6:23 Marco Atzeri
2017-07-02 9:54 ` JonY
2017-07-03 10:22 ` Marco Atzeri
2017-07-03 13:32 ` JonY
2017-07-03 15:41 ` Marco Atzeri
2017-07-04 21:17 ` Marco Atzeri [this message]
2017-07-05 22:50 ` JonY
2017-07-06 6:53 ` Marco Atzeri
2017-07-06 13:41 ` JonY
2017-07-06 16:30 ` Marco Atzeri
2017-07-09 4:29 ` JonY
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9acd520b-b080-2938-1e12-b61280f33a3f@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).