search for: dicier

2015-03-03 0:43 GMT+02:00 Tim Dunphy <bluethundr at gmail.com>: > > > > errr, I meant, sftp, not rscp > > > Heh.. yeah. But the client isn't gonna go for that. LOL. Any way to allow > regular ol' FTP using SELinux? Or does that just defeat the purpose of > having a secure SELlinux server entirely? > FTP is not safe as it does not encrypt username(s)

...icult to make work. Even factoring in the llvm-dwarfdump part, it has to understand the selector only for the .debug_aranges section; everything else can remain as it is, pretending there’s a flat address space. Now, if your target is downstream, that would make upstreaming the LLVM support a bit dicier, because we’d not want to have that feature in the upstream repo if there are no targets using it. You’d be left maintaining that patch on your own. But as I described above, I don’t think it would be a huge deal. HTH, --paulr From: David Blaikie <dblaikie at gmail.com> Sent: Thursday, Ma...

..., it has to understand the selector only for the .debug_aranges >> section; everything else can remain as it is, pretending there’s a flat >> address space. >> >> >> >> Now, if your target is downstream, that would make upstreaming the LLVM >> support a bit dicier, because we’d not want to have that feature in the >> upstream repo if there are no targets using it. You’d be left maintaining >> that patch on your own. But as I described above, I don’t think it would >> be a huge deal. >> >> >> >> HTH, >> >&g...

Hi, Kbytes RSS rNo 2689632 1450876 1433788 2689632 1450876 1433788 2689632 1450876 1433788 2689632 1450876 1433788 2689632 1450876 1433788 2689632 1450876 1433788 2689632 1450876 1433788 2689632 1460168 1443084 plot(data$rNo,data$RSS,pch=0,type="b",col=36,axes=FALSE, ylab="", xlab="",las=2,lwd=2.5) title(" PID -

On Thu Mar 12, 2020 at 5:37 PM, David Blaikie wrote: > On Wed, Mar 11, 2020 at 8:09 AM Luke Drummond > <luke.drummond at codeplay.com> > wrote: > > > On Tue Mar 10, 2020 at 7:45 PM, David Blaikie wrote: > > > If you only want code addresses, why not use the CU's > > > low_pc/high_pc/ranges > > > - those are guaranteed to be only code

...the llvm-dwarfdump > part, it has to understand the selector only for the .debug_aranges > section; everything else can remain as it is, pretending there’s a flat > address space. > > > > Now, if your target is downstream, that would make upstreaming the LLVM > support a bit dicier, because we’d not want to have that feature in the > upstream repo if there are no targets using it. You’d be left maintaining > that patch on your own. But as I described above, I don’t think it would > be a huge deal. > > > > HTH, > > --paulr > > > > *From...