Displaying 4 results from an estimated 4 matches for "l364".
Did you mean:
364
2019 May 23
2
Proposal for Mach-O support in llvm-objcopy: section renaming
...cho-names --only-secton=__TEXT.__text a.out
OK: llvm-objcopy --macho-names --only-secton=__TEXT,__text a.out
What do you think about this behavior?
Thanks,
Seiya
[1]: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=bfd/mach-o.c;h=d9edef2871d83b53280b613935c068e4327f3270;hb=HEAD#l364
[2]: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=bfd/mach-o.c;h=d9edef2871d83b53280b613935c068e4327f3270;hb=HEAD#l90
2019 May 23
3
Proposal for Mach-O support in llvm-objcopy: section renaming
...out
> OK: llvm-objcopy --macho-names --only-secton=__TEXT,__text a.out
>
> What do you think about this behavior?
>
> Thanks,
> Seiya
>
> [1]: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=bfd/mach-o.c;h=d9edef2871d83b53280b613935c068e4327f3270;hb=HEAD#l364 <https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=bfd/mach-o.c;h=d9edef2871d83b53280b613935c068e4327f3270;hb=HEAD#l364>
> [2]: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=bfd/mach-o.c;h=d9edef2871d83b53280b613935c068e4327f3270;hb=HEAD#l90 <https://...
2015 Jun 25
2
Re: [PATCH] launch: rework handling of --enable-valgrind-daemon
In data giovedì 25 giugno 2015 14:50:03, Richard W.M. Jones ha scritto:
> We had a chat about this on IRC, and I'm not very happy about any
> patch that requires a special ./configure flag.
I'm not sure where you see any special ./configure flag, other than
what is already there (and not used much because makes things
cumbersome).
> We should find a way
> to enable this
2015 Jun 25
0
Re: [PATCH] launch: rework handling of --enable-valgrind-daemon
...on the parts you consider racy?
There are two objections:
(1) That we currently have separate shutdown paths in the
valgrind/non-valgrind case:
https://github.com/libguestfs/libguestfs/blob/master/src/handle.c#L429-L443
https://github.com/libguestfs/libguestfs/blob/master/src/conn-socket.c#L346-L364
We shouldn't have two different paths that developers and non-
developers use.
(2) This actually causes bugs. The second one is the race.
https://bugzilla.redhat.com/show_bug.cgi?id=1023630
https://bugzilla.redhat.com/show_bug.cgi?id=1020216
There's also another race which I don't...