Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect collisions in user code linked against 3rd-party static lib #5

Open
Artalus opened this issue May 7, 2018 · 0 comments
Open
Labels
enhancement New feature or request question Further information is requested

Comments

@Artalus
Copy link
Owner

Artalus commented May 7, 2018

class RealisationDetail {
  int x;
  void set(int v) { x = v; }
};

///lib.h
class TotallyOk {};
///lib.a
class ImplementationDetail {
  const char buffer[256];
  void set(const char *str) { ... }
}

...Is this even collision, or would linker be smart enough to separate those? And if it is, are there any options besides emitting ODR-1338: file.cpp: defining symbol X, while lib.a also has symbol X exported?
It also would need some crossplatform readelf or nm to work.

@Artalus Artalus added question Further information is requested enhancement New feature or request labels May 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant