similar to: Evaluating a port to RTEMS (embedded OS with single address space and no processes)

Am 04.02.2016 um 14:46 schrieb Roland Mainz: > On Thu, Feb 4, 2016 at 1:40 PM, Christian Mauderer > <christian.mauderer at embedded-brains.de> wrote: >> I am searching a SSH server for remote administration of an embedded >> application running on RTEMS (https://www.rtems.org). This environment >> has neither virtual memory nor user and kernel space. So this is like

Hi Walter, I've done a first quick scan. Overall looks reasonable, but I'd like to try reducing the number of newly introduced platform-specific ifs. Vitaly, please also take a look (once my initial comments are addressed). One outstanding issue is your problem with initialization vs checking, which requires you to insert so many ifs. Is there any chance you can avoid this? If you

Hey, I work on fuchsia symbolizer stuff. I don't know if you guys already have an external symbolizer but I'm working on making one right now and I plan on making one backed by LLVM that can be run host-side or target-side. I'd like to contribute that back to llvm ideally. What do you guys have so far? I have a prototype in golang that just spins up an instance of llvm-symbolizer

Hi Jake. Thanks for the info. Where can I keep up to date on the symbolizer status? Our symbolizer is provided by the Myriad vendor and integrated into its host test environment. It doesn't do much: just look for PC string patterns and symbolize them using addr2line. Thanks, Walter On Fri, May 4, 2018 at 5:36 PM Jake Ehrlich <jakehehrlich at google.com> wrote: > Hey, > I

Hi Kostya. Thanks for the quick feedback. I will work on addressing your comments. In regard to initialization checks, I can eliminate most of them by initializing the shadow memory very early, but I still need to do something in two places, __asan_handle_no_return and GetFakeStackFast. Would it be ok to have guards for those two places only? Walter On Fri, May 4, 2018 at 6:10 PM Kostya

I have ported ASan in LLVM to Myriad RTEMS, and I would like to upstream the port. Below is the design doc. Feedback welcome. https://docs.google.com/document/d/1oxmk0xUojybDaQDAuTEVpHVMi5xQX74cJPyMJbaSaRM The port is expected to work with modified versions of RTEMS and newlib. I have a git repo with changes to those projects, that I can make available if there is interest. Here is the patch

On 2 January 2018 at 17:08, Marc Haber <mh+openssh-unix-dev at zugschlus.de> wrote: > On Tue, Jan 02, 2018 at 04:03:34PM +1030, David Newall wrote: >> On 02/01/18 03:29, Michael Str?der wrote: >> > How high is the risk that this unmaintained device is added to >> > yet-another-bot-net in the Internet-of-shitty-devices or is used to >> > enter parts of your

Hello, I am wondering are there plans for porting WINEHQ to AmigaOS 4.x running on PPC? 1) http://amigakit.leamancomputing.com/catalog/product_info.php?cPath=47&products_id=826 2) http://amigakit.leamancomputing.com/catalog/images/osfour_shots/shot1.jpg 3) http://amigakit.leamancomputing.com/catalog/images/osfour_shots/shot2.jpg 4)

Hi, I'd like to load with pxelinux an RTEMS executable file, the format is ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, strtipped Can someone tell me if there is a way to load it with PXElinux. When I try to do it, the error message is : invalid or corrupt kernel image Thanks for your help. Regards. Stephane ARQUER

On Fri, May 4, 2018 at 6:29 PM Walter Lee <waltl at google.com> wrote: > Hi Kostya. Thanks for the quick feedback. I will work on addressing your > comments. > > In regard to initialization checks, I can eliminate most of them by > initializing the shadow memory very early, This will be a very good way to handle this. > but I still need to do something > in two

Hello!, I have succesfuly compiled OpenSSH on the AmigaOS platform.....all seems to work fine by now...except by sshd, it fail in monitor.c(monitor_sockletpair): socketpair() func with errno #46...so, I was wondering if there is some alternative I can use here ?. any help appreciated. Kind regards ps.: excuse my bad english.. -- Diego CR - http://Amiga.SourceForge.net

On 23 April 2014 21:43, mancha <mancha1 at zoho.com> wrote: > On Wed, Apr 23, 2014 at 12:26:58PM -0700, Iain Morgan wrote: >> A slightly better solution would be a PAM module that uses the same >> syntax as libwrap. Possibly someone has already written such a module. > > Possibly, but only for platforms which use for PAM. Pam is executed so late in the chain that any

On RAM... You chose the 32-byte shadow granularity to reduce the RAM overhead, but I am afraid this will actually increase it due to extra alignment requirements, especially if an average allocation on your typical application is small. The pointers are 32-bit, right? Given how RAM-constrained your environment is, maybe you should consider something more like HWASAN instead of ASAN.

On Fri, May 4, 2018 at 6:21 PM Kostya Serebryany <kcc at google.com> wrote: > On RAM... > You chose the 32-byte shadow granularity to reduce the RAM overhead, > but I am afraid this will actually increase it due to extra alignment requirements, > especially if an average allocation on your typical application is small. Good point. I will run our test suite with 8-byte shadow

On Mon, May 7, 2018 at 12:35 PM Walter Lee <waltl at google.com> wrote: > On Mon, May 7, 2018 at 2:05 PM Kostya Serebryany <kcc at google.com> wrote: > >> >> >>> and GetFakeStackFast. >> >> >> Not sure. Why don't just disable stack-use-after-return? >> > > Yeah originally I was going to do that, but: > I probably

On Mon, May 7, 2018 at 2:05 PM Kostya Serebryany <kcc at google.com> wrote: > > >> and GetFakeStackFast. > > > Not sure. Why don't just disable stack-use-after-return? > Yeah originally I was going to do that, but: 1. We had a stack use-after-return last month that people had to debug by hand. that would have been caught by ASan with stack-use-after-return. So

I ran our test suite with grain of 8 and 32, and more tests were able to avoid running out of memory with grain of 32 than 8. The ones that run out of memory on 8 but not 32 all failed trying to allocate a large region from the heap (350M). I haven't had any tests that run out of memory for other reasons. Given that, I will check in the current selected granularity of 32. I will try grain

On Thu, 10 Aug 2023, Cedric Blancher wrote: >We're experiencing rather very bad latency spikes on busy Linux >systems, for example if one machine is the jumphost (ssh -J) for a few >hundred connections, while at the same time handles CPU intensive >tasks. > >Would RT/Linux SCHED_FIXED or SCHED_RR be of help in such a case, e.g. Did you already check the old and tried method

Hi, Would anyone be interested in developing a LatticeMico32 backend in LLVM? LatticeMico32 [1] is an open source microprocessor core designed by Lattice Semiconductor and typically used in FPGAs. It is comparable to the Microblaze processor that you already support. It is already supported by GNU Binutils and GCC (4.5+). It is used by the Milkymist [2] and RTEMS [3] projects. The Milkymist

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:08.realpath Security Advisory The FreeBSD Project Topic: Single byte buffer overflow in realpath(3) Category: core Module: libc Announced: