| Summary: | ASTERISK-06521: [patch] Fully initialize NULL frames | ||
| Reporter: | Tilghman Lesher (tilghman) | Labels: | |
| Date Opened: | 2006-03-11 00:47:07.000-0600 | Date Closed: | 2006-03-14 11:28:30.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) 20060311__initialize_null_frames.diff.txt | |
| Description: | We've had a number of difficult-to-track bugs where it appears that we're freeing frames that were never malloc'd, hence causing a crash. One such problem might be that we are not sufficiently initializing NULL frames, such that the mallocd flag may be erroneously non-zero. This patch simply changes the initialization of null frames in various places to completely zero the structure. This should eliminate one possible problem which could result in mysterious crashes. | ||
| Comments: | By: Russell Bryant (russell) 2006-03-14 11:02:14.000-0600 I thought that if you initialize any part of a structure, you can assume that the rest is automatically initialized to zero. This assumption is made all over the place in Asterisk. By: Tilghman Lesher (tilghman) 2006-03-14 11:28:30.000-0600 Oops, you're right. Never mind. | ||