diff options
| author | jpeeler <jpeeler@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-12-01 22:00:14 +0000 |
|---|---|---|
| committer | jpeeler <jpeeler@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-12-01 22:00:14 +0000 |
| commit | 54e1f2cb78115226c098e5eb5fa7cc2b5b573dd5 (patch) | |
| tree | b3911d671bb3ba9e4c7aca4729ed33407c0b3041 /funcs | |
| parent | 4879a39a9aec28f8b9c427cf473fccfd071c9bf5 (diff) | |
Merged revisions 231927 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk
................
r231927 | jpeeler | 2009-12-01 15:54:21 -0600 (Tue, 01 Dec 2009) | 19 lines
Merged revisions 231911 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r231911 | jpeeler | 2009-12-01 15:29:31 -0600 (Tue, 01 Dec 2009) | 12 lines
Fix crash with invalid frame data
The crash was happening as a result of a frame containing an invalid data
pointer, but was set with data length of zero. The few times the issue was
reproduced it _seemed_ that the frame was queued properly, that is the data
pointer was set to NULL. I never could reproduce the crash so as a last resort
the crash has been fixed, but a check in __ast_read has been added to give as
much information about the source of problematic frames in the future.
(closes issue #16058)
Reported by: atis
........
................
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.1@231929 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'funcs')
0 files changed, 0 insertions, 0 deletions