This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libsanitizer merge from upstream r208536


I've checked all available systems and wasn't able to repro this.

Given your exchanges with Jakub I thought that at this point it was
clear that the issue is real.

There are three issues here:
1) whether warning should cause termination
2) whether warning should be displayed by default
3) why warning occurs on your machine

We mainly discussed 1 and 2 with Jakub but even if we hide this warning it still should have come up on your machine in the first place. It's either false positive which needs to be fixed or symptom of some real problem. I believe it still makes sense to investigate the original problem.

Every time vDSO was already filtered with

  if (!info->dlpi_name || info->dlpi_name[0] == 0)
    return 0;

in FindFirstDSOCallback.

Could you provide additional details of your setup? Or perhaps print
dlpi_name of offending library?

How do I print dlpi_name?

Could you add something like
  Report("'%s'\n", info->dlpi_name);
after
  if (!info->dlpi_name || info->dlpi_name[0] == 0)
check in FindFirstDSOCallback? This should give us the name of library which causes problems.

And which detail do you want?

Just the name of the library.

It's a very,
very, standard Linux machine, running a 3.11.10 kernel and a 2.18 glibc,
two days ago everything was fine, 4_9-branch is fine.

True but being unable to repro this, I'd need some additional help to diagnose the problem.

-Y


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]