https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #40 from Dmitry Vyukov ---
Phil, please move the discussion to:
https://groups.google.com/forum/#!forum/thread-sanitizer
This is not gcc specific, and more people will be able to see it in the tsan
group.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #39 from Dmitry Vyukov ---
>Isomalloc works best when we can assure it as large a range of common,
>unoccupied virtual address space as possible. Thus, it's much happier when
>ASLR is disabled.
I do not follow you here. How does AS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
Phil Miller changed:
What|Removed |Added
CC||unmobile at gmail dot com
--- Comment #38
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #37 from H.J. Lu ---
(In reply to Kostya Serebryany from comment #36)
> While we are at it, H.J., is there any hope with
> https://bugzilla.kernel.org/show_bug.cgi?id=66721 ?
I will see what I can do.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #36 from Kostya Serebryany ---
While we are at it, H.J., is there any hope with
https://bugzilla.kernel.org/show_bug.cgi?id=66721 ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
Dmitry Vyukov changed:
What|Removed |Added
CC||dvyukov at google dot com
--- Comment #3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #33 from Jakub Jelinek ---
Author: jakub
Date: Fri Jan 31 21:25:23 2014
New Revision: 207371
URL: http://gcc.gnu.org/viewcvs?rev=207371&root=gcc&view=rev
Log:
PR sanitizer/59410
* lib/tsan-dg.exp (tsan_init): Instead of not ru
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #32 from Yury Gribov ---
Jakub has posted patch which may fix this:
http://gcc.gnu.org/ml/gcc-patches/2014-01/msg02044.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #31 from H.J. Lu ---
(In reply to Jakub Jelinek from comment #29)
> It is not that easy. gold before February 2013 doesn't grok -Ttext-segment,
> you need -Ttext there instead. See
> http://gcc.gnu.org/ml/gcc-patches/2013-02/msg00777
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #30 from Kostya Serebryany ---
We could add -Ttext-segment=0x7d00 (not 0x8500!),
to either the tests or the driver, but
a) see Jakub's comment about Gold
b) it will not fix anything, and
c) it will not help when ASLR is
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #29 from Jakub Jelinek ---
It is not that easy. gold before February 2013 doesn't grok -Ttext-segment,
you need -Ttext there instead. See
http://gcc.gnu.org/ml/gcc-patches/2013-02/msg00777.html
And, given that gcc can be configured t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #28 from Yury Gribov ---
(In reply to H.J. Lu from comment #26)
> TSAN tests should specify a load address which
> works with TSAN.
We'll add `-Wl,-Ttext-segment,0x8500' to TSan tests compilation options
then.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
Yury Gribov changed:
What|Removed |Added
CC||y.gribov at samsung dot com
--- Comment #27
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #26 from H.J. Lu ---
(In reply to Kostya Serebryany from comment #25)
> > https://bugzilla.kernel.org/show_bug.cgi?id=66721
>
> Good! Looking forward for a fix and hoping to have it in the next Ubuntu LTS.
> Any chance?
> Is there an
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #25 from Kostya Serebryany ---
> https://bugzilla.kernel.org/show_bug.cgi?id=66721
Good! Looking forward for a fix and hoping to have it in the next Ubuntu LTS.
Any chance?
Is there anything else we could do with this tsan issue?
(gi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #24 from H.J. Lu ---
(In reply to Kostya Serebryany from comment #22)
> > That is true. The kernel change was made to fix:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=36372
>
> Could you please explain the situation?
> What
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #23 from H.J. Lu ---
I opened:
https://bugzilla.kernel.org/show_bug.cgi?id=66721
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #22 from Kostya Serebryany ---
> That is true. The kernel change was made to fix:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=36372
Could you please explain the situation?
What was fixed and in which kernel?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #21 from H.J. Lu ---
(In reply to Kostya Serebryany from comment #20)
> > >
> > > # readelf -lW a.out
> >
> > Your address must be sensible. Otherwise kernel will ignore it.
> > Please try "-Ttext-segment 0x8500".
>
> How i
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #20 from Kostya Serebryany ---
> >
> > # readelf -lW a.out
>
> Your address must be sensible. Otherwise kernel will ignore it.
> Please try "-Ttext-segment 0x8500".
How is 0x8500 censible if it's beyond the address
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
--- Comment #19 from H.J. Lu ---
(In reply to H.J. Lu from comment #18)
> (In reply to Kostya Serebryany from comment #16)
> > > Kernel is free to load PIE at ANY address it wants. But
> > > you can specify where to load PIE via a linker switch
>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59410
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
23 matches
Mail list logo
