Back to bug 1007614
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Laszlo Ersek | 2013-09-13 00:10:59 UTC | Severity | medium | high |
| Larry Troan | 2013-12-16 21:34:18 UTC | CC | ltroan | |
| Blocks | 1020419 | |||
| Larry Troan | 2013-12-16 21:34:45 UTC | Priority | unspecified | medium |
| Tom Lavigne | 2014-03-03 19:43:18 UTC | Blocks | 1056252 | |
| Martin Cermak | 2014-04-07 13:45:12 UTC | CC | mcermak | |
| Sergio Durigan Junior | 2014-04-16 04:35:29 UTC | Status | NEW | MODIFIED |
| Laura Novich | 2014-04-30 09:44:28 UTC | Blocks | 1092931 | |
| Sergio Durigan Junior | 2014-06-03 22:08:12 UTC | Fixed In Version | gdb-7.2-67.el6 | |
| errata-xmlrpc | 2014-06-11 23:36:25 UTC | Status | MODIFIED | ON_QA |
| Miroslav Franc | 2014-07-10 12:36:36 UTC | Status | ON_QA | VERIFIED |
| Lubos Kocman | 2014-07-22 17:07:22 UTC | Depends On | 1122165 | |
| John Shortt | 2014-07-22 17:57:00 UTC | Depends On | 1122165 | |
| John Skeoch | 2014-08-11 05:47:18 UTC | CC | tromey | patrickm |
| Sergio Durigan Junior | 2014-09-24 17:32:13 UTC | Doc Text | Cause: A specific function in the Python support on GDB leaked the reference to a buffer that was read from the program being debugged. Consequence: In a memory-intensive scenario, GDB would leak a big amount of memory. Fix: GDB now correctly frees the memory acquired. Result: GDB does not overconsume memory when using Python scriptting on memory-intensive scenarios. |
|
| errata-xmlrpc | 2014-10-14 07:28:03 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-10-14 03:28:03 UTC |
Back to bug 1007614