Google Git
Sign in
pigweed / third_party / github / FreeRTOS / FreeRTOS-Kernel / baeb5af9a4d8b34c39edd2a5d72abf7661e7eb9a
commitbaeb5af9a4d8b34c39edd2a5d72abf7661e7eb9a[log] [tgz]
authorReda Maher <52288047+RedaMaher@users.noreply.github.com>Tue Sep 29 23:06:10 2020 +0200
committerGitHub <noreply@github.com>Tue Sep 29 14:06:10 2020 -0700
treef1da41442877ab78f28b019fee67ca5fa51e527a
parent2225bb5620c883211b2afc3dab404bafbc07dd0f [diff]
Posix: Free the allocated memory after deleting a task or ending the scheduler (#181)

* Posix: Free Idle task resources after ending the scheduler

In case of using Posix simulator and ending the scheduler, it does
not free the resources allocated by the idle task. This
causes the memory checkers (Valgrind, Address Sanitizers, ..) to
complain.

* Posix: Free the condition variable memory in the correct place

In case of deleting a task from another task, the deletion happens
immediately and the thread is canceled but the memory allocated by
the task condition variable is not freed. This causes the memory
checkers (Valgrind, Address sanitizers, ..) to complain.

* Posix: End Timer thread and free its resources after ending the scheduler
1 file changed
tree: f1da41442877ab78f28b019fee67ca5fa51e527a
  1. .github/
  2. include/
  3. portable/
  4. CONTRIBUTING.md
  5. croutine.c
  6. event_groups.c
  7. GitHub-FreeRTOS-Kernel-Home.url
  8. History.txt
  9. lexicon.txt
  10. LICENSE.md
  11. list.c
  12. queue.c
  13. Quick_Start_Guide.url
  14. README.md
  15. SECURITY.md
  16. stream_buffer.c
  17. tasks.c
  18. timers.c
README.md

Getting started

This repository contains FreeRTOS kernel source/header files and kernel ports only. This repository is referenced as a submodule in FreeRTOS/FreeRTOS repository, which contains pre-configured demo application projects under FreeRTOS/Demo directory.

The easiest way to use FreeRTOS is to start with one of the pre-configured demo application projects. That way you will have the correct FreeRTOS source files included, and the correct include paths configured. Once a demo application is building and executing you can remove the demo application files, and start to add in your own application source files. See the FreeRTOS Kernel Quick Start Guide for detailed instructions and other useful links.

Additionally, for FreeRTOS kernel feature information refer to the Developer Documentation, and API Reference.

Getting help

If you have any questions or need assistance troubleshooting your FreeRTOS project, we have an active community that can help on the FreeRTOS Community Support Forum.

Cloning this repository

To clone using HTTPS:

git clone https://github.com/FreeRTOS/FreeRTOS-Kernel.git

Using SSH:

git clone git@github.com:FreeRTOS/FreeRTOS-Kernel.git

Repository structure

  • The root of this repository contains the three files that are common to every port - list.c, queue.c and tasks.c. The kernel is contained within these three files. croutine.c implements the optional co-routine functionality - which is normally only used on very memory limited systems.

  • The ./portable directory contains the files that are specific to a particular microcontroller and/or compiler. See the readme file in the ./portable directory for more information.

  • The ./include directory contains the real time kernel header files.

Code Formatting

FreeRTOS files are formatted using the “uncrustify” tool. The configuration file used by uncrustify can be found in the FreeRTOS/FreeRTOS repository.

Spelling

lexicon.txt contains words that are not traditionally found in an English dictionary. It is used by the spellchecker to verify the various jargon, variable names, and other odd words used in the FreeRTOS code base. If your pull request fails to pass the spelling and you believe this is a mistake, then add the word to lexicon.txt. Note that only the FreeRTOS Kernel source files are checked for proper spelling, the portable section is ignored.