Testing posting of issues #2
Comments
Closed
mxxo
added a commit
to mxxo/EGSnrc
that referenced
this issue
Jul 27, 2021
After compiling egs_view with asan support, there was a buffer overflow
error traced back to the memcpy call in ImageWindow::paintEvent.
```
ERROR: AddressSanitizer: dynamic-stack-buffer-overflow ...
READ of size 400 at 0x7ffe71889e40 thread T0
#0 0x7f543595ecdf (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x99cdf)
nrc-cnrc#1 0x55dc3acdbb15 in memcpy
nrc-cnrc#2 0x55dc3acdbb15 in ImageWindow::paintEvent(QPaintEvent*)
nrc-cnrc#3 0x7f5434f86047 in QWidget::event(QEvent*)
```
The issue is that memcpy will always copy sizeof(lastRegions) bytes,
into the array `regions`, but before this change `regions` could be
shorter than `lastRegions`, leading to a buffer overflow. After this
change, `maxreg` is always set to `N_REG_MAX`, the length of
`lastRegions`.
ftessier
pushed a commit
to mxxo/EGSnrc
that referenced
this issue
Jun 27, 2022
After compiling egs_view with asan support, there was a buffer overflow
error traced back to the memcpy call in ImageWindow::paintEvent.
ERROR: AddressSanitizer: dynamic-stack-buffer-overflow ...
READ of size 400 at 0x7ffe71889e40 thread T0
#0 0x7f543595ecdf (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x99cdf)
nrc-cnrc#1 0x55dc3acdbb15 in memcpy
nrc-cnrc#2 0x55dc3acdbb15 in ImageWindow::paintEvent(QPaintEvent*)
nrc-cnrc#3 0x7f5434f86047 in QWidget::event(QEvent*)
The issue is that memcpy will always copy sizeof(lastRegions) bytes,
into the array regions, but before this change regions could be shorter
than lastRegions, leading to a buffer overflow. After this change,
maxreg is always set to N_REG_MAX, the length of lastRegions.
ftessier
pushed a commit
to mxxo/EGSnrc
that referenced
this issue
Jun 27, 2022
After compiling egs_view with asan support, there was a buffer overflow
error traced back to the memcpy call in ImageWindow::paintEvent.
ERROR: AddressSanitizer: dynamic-stack-buffer-overflow ...
READ of size 400 at 0x7ffe71889e40 thread T0
#0 0x7f543595ecdf (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x99cdf)
nrc-cnrc#1 0x55dc3acdbb15 in memcpy
nrc-cnrc#2 0x55dc3acdbb15 in ImageWindow::paintEvent(QPaintEvent*)
nrc-cnrc#3 0x7f5434f86047 in QWidget::event(QEvent*)
The issue is that memcpy will always copy sizeof(lastRegions) bytes into
the array regions. But before this change, regions could be shorter than
lastRegions, leading to a buffer overflow. After this change, maxreg is
always set to N_REG_MAX, the length of lastRegions.
ftessier
pushed a commit
to mxxo/EGSnrc
that referenced
this issue
Jun 27, 2022
After compiling egs_view with asan support, there was a buffer overflow
error traced back to the memcpy call in ImageWindow::paintEvent.
ERROR: AddressSanitizer: dynamic-stack-buffer-overflow ...
READ of size 400 at 0x7ffe71889e40 thread T0
#0 0x7f543595ecdf (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x99cdf)
nrc-cnrc#1 0x55dc3acdbb15 in memcpy
nrc-cnrc#2 0x55dc3acdbb15 in ImageWindow::paintEvent(QPaintEvent*)
nrc-cnrc#3 0x7f5434f86047 in QWidget::event(QEvent*)
The issue is that memcpy will always copy sizeof(lastRegions) bytes into
the array regions. But before this change, regions could be shorter than
lastRegions, leading to a buffer overflow. After this change, maxreg is
always set to N_REG_MAX, the length of lastRegions.
ftessier
pushed a commit
that referenced
this issue
Jun 30, 2022
After compiling egs_view with asan support, there was a buffer overflow
error traced back to the memcpy call in ImageWindow::paintEvent.
ERROR: AddressSanitizer: dynamic-stack-buffer-overflow ...
READ of size 400 at 0x7ffe71889e40 thread T0
#0 0x7f543595ecdf (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x99cdf)
#1 0x55dc3acdbb15 in memcpy
#2 0x55dc3acdbb15 in ImageWindow::paintEvent(QPaintEvent*)
#3 0x7f5434f86047 in QWidget::event(QEvent*)
The issue is that memcpy will always copy sizeof(lastRegions) bytes into
the array regions. But before this change, regions could be shorter than
lastRegions, leading to a buffer overflow. After this change, maxreg is
always set to N_REG_MAX, the length of lastRegions.
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
ftessier
added a commit
that referenced
this issue
Jul 12, 2022
Add a compilation test configuration file for continuous integration, similar to Travis-CI (file .travis.yaml in project root directory), but running as a github action instead. # This is the commit message #2:
mchamberland
pushed a commit
to mchamberland/EGSnrc
that referenced
this issue
Jul 11, 2023
Changing rad generation weighting
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is just to test how issues posted by EGSnrc users will show up in the EGSnrc repository issues pages.
The text was updated successfully, but these errors were encountered: