wkwood (Will Wood)
- Login: wkwood
- Email: wkwood@gmail.com
- Registered on: 07/09/2014
- Last sign in: 07/30/2014
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
07/30/2014
-
04:48 PM Ruby Bug #10019: segmentation fault/buffer overrun in pack.c (encodes)
- Well the reproducibility issue appears to be a toolset problem. If I build with -O2 the code works fine. I think ultimately the optimizations (O3) for gcc 4.7.2 at least with the mingw toolset are causing the issue here for windows. I...
07/28/2014
-
- I took a look at it yesterday. Here's the issue. In the loop (len >= 3) you check to see if there's enough room in buff. Unfortunately if len < 3 we don't flush the buffer and then write additional bytes onto
the end without checking...
07/23/2014
-
- I agree the argument should be short. I'm working on it, but it's definitely strange. If I take the buffer and allocate it off the heap it's fine. Maybe it's a build
issue with RubyInstaller? Anyway, I'll poke around with and get ba...
07/19/2014
-
- After pulling the latest code, your fix still causes a seg fault. IMO you're still overrunning the buffer.
~~~
d:/ruby-2.1.2-i386-mingw32/lib/ruby/2.1.0/base64.rb:38: [BUG] Segmentation fault
ruby 2.1.2p176 (2014-07-19 revision 4686...
07/09/2014
-
- While working with an AWS sample I hit a segmentation fault. The same sample works under 1.9.3. It appeared to be coming from pack.c function encodes. After looking at the source there's a 4K buffer allocated on the stack. I made a m...