-
Notifications
You must be signed in to change notification settings - Fork 19
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
Memory leak not reported #836
Labels
Comments
BTW this problem happens on both old and new Seashell versions. |
yc2lee
added a commit
to yc2lee/seashell
that referenced
this issue
Nov 23, 2017
* Hack around issue cs136#836 by using clang executable, which finds the memory leak properly * Log out button should go back to Seashell sign-in page instead of CAS * Update sign-in page with supported browsers and better "wrong password" message * Disable offline mode
I suspect the issue is we may be missing a flag that clang passes to cc1
when asan is used.
I think there’s a flag to turn on verbose mode to see what flags are passed
to cc1.
…On Fri, Nov 17, 2017 at 5:00 PM yc2lee ***@***.***> wrote:
BTW this problem happens on both old and new Seashell versions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#836 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADK8ihHB1UA0POV9DdtfBHylU97qfh1bks5s3gIPgaJpZM4QfK3K>
.
|
Alright, unfortunately it's not as simple as flag errors. The backend
generates code in a way that is slightly different than stock clang (we
link all the intermediate LLVM modules together before
writing an object file).
Your best bet to fix this is to have the backend write LLVM bitcode to the
intermediate object file, instead of writing a standard object file.
`final_link_step` has all the code necessary to do this,
as the emscripten version of seashell-clang generates LLVM bitcode files,
which is nice, as you can simplify `final_link_step`. You'll also have to
change the extension of the temporary object file to `.bc` from `.o`.
Finally, you'll have to set some additional compiler flags and ASAN runtime
options as ASan needs some additional help when running with files
generated this way.
google/sanitizers#647 has the details.
…On Thu, Nov 23, 2017 at 4:39 PM, Edward Lee ***@***.***> wrote:
I suspect the issue is we may be missing a flag that clang passes to cc1
when asan is used.
I think there’s a flag to turn on verbose mode to see what flags are
passed to cc1.
On Fri, Nov 17, 2017 at 5:00 PM yc2lee ***@***.***> wrote:
> BTW this problem happens on both old and new Seashell versions.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#836 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADK8ihHB1UA0POV9DdtfBHylU97qfh1bks5s3gIPgaJpZM4QfK3K>
> .
>
--
Edward Lee
|
yc2lee
added a commit
that referenced
this issue
Nov 24, 2017
Old Seashell (v3) Updates: * Hack around issue #836 by using clang executable, which finds the memory leak properly * Log out button should go back to Seashell sign-in page instead of CAS * Update sign-in page with supported browsers and better "wrong password" message * Disable offline mode
yc2lee
added a commit
to yc2lee/seashell
that referenced
this issue
Nov 27, 2017
…e memory leak properly
yc2lee
added a commit
that referenced
this issue
Nov 28, 2017
Hack around issue #836 by using clang executable, which finds the memory leak properly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following code generates a memory leak error, which it's supposed to do.
But if you uncomment the definition of i and use malloc(i), no memory leaks are reported.
The problem is not ASAN parser because the binary executable created by Seashell does not report any errors either.
The text was updated successfully, but these errors were encountered: