- 浏览: 604371 次
- 性别:
- 来自: 杭州
文章分类
最新评论
-
oldrat:
引用Special cases aren't special ...
武汉大学开源技术俱乐部 技术交流 第1期 -
yzsunlight:
试了试 ,不行
Android Studio SDK Manager无法正常下载如何设置 -
qianjigui:
更全面的文档:http://www.5wpc.info/it/ ...
Ruby正则表达式操作参考 -
qianjigui:
Anddy 写道Anddy 写道tag是自动创建的吗? 能手动 ...
vim的跳转 -
Anddy:
Anddy 写道tag是自动创建的吗? 能手动创建吗? 在sh ...
vim的跳转
Debugging Malloc Lab: Detecting Memory-Related Errors
Introduction
The usual implementation of malloc and free are unforgiving to errors in their callers' code, including cases where the programmer overflows an array, forgets to free memory, or frees a memory block twice. This often does not affect the program immediately, waiting until the corrupted memory is used later (in the case of overwrites) or gradually accumulating allocated but unused blocks. Thus, debugging can be extremely difficult.
In this assignment, you will write a wrapper for the malloc package that will catch errors in the code that calls malloc and free. The skills you will have learned upon the completion of this exercise are pointer arithmetic and a greater understanding of the consequences of subtle memory mistakes.
Logistics
Unzip debugging_malloc.zip into an empty directory. The files contained are as follows:
File(s): Function: debugmalloc.c Contains the implementation of the three functions you will be writing. This is the one file you will be editing and handing in. debugmalloc.h Contains the declaration of the functions, as well as the macros that will call them. driver.c Contains main procedure and the code that will be calling the functions in the malloc package dmhelper.c , dmhelper.h Contain the helper functions and macros that you will be calling from your code grader.pl Perl script that runs your code for the various test cases and gives you feedback based on your current code debugmalloc.vcproj Project file tailor.h , getopt.c , getopt.h Tools that are used only by the driver program for I/O purposes. You will not need to know what the code in these files do.
Specification
Programs that use this package will call the macros MALLOC and FREE . MALLOC and FREE are used exactly the same way as the malloc() and free() functions in the standard C malloc package. That is, the line
void *ptr = MALLOC(n);
will allocate a payload of at least n bytes, and ptr will point to the front of this block. The line
FREE(ptr);
will cause the payload pointed to by ptr to be deallocated and become available for later use. The macros are defined as follows:
#define MALLOC(s) MyMalloc(s, __FILE__, __LINE__) #define FREE(p) MyFree(p, __FILE__, __LINE__)
The __FILE__ macro resolves to the filename and __LINE__ resolves to the current line number. The debugmalloc.c file contains three functions that you are required to implement, as shown:
void *MyMalloc(size_t size, char *filename, int linenumber); void MyFree(void *ptr, char *filename, int linenumber); int AllocatedSize();
Using the macros above allow MyMalloc and MyFree to be called with the filename and line number of the actual MALLOC and FREE calls, while retaining the same form as the usual malloc package. By default, MyMalloc and MyFree() simply call malloc() and free() , respectively, and return immediately. AllocatedSize() should return the number of bytes currently allocated by the user: the sum of the requested bytes through MALLOC minus the bytes freed using FREE . By default, it simply returns 0 and thus is unimplemented. The definitions are shown below:
void *MyMalloc(size_t size, char *filename, int linenumber) { return (malloc(size)); } void MyFree(void *ptr, char *filename, int linenumber) { free(ptr); } int AllocatedSize() { return 0; }
Your job is to modify these functions so that they will catch a number of errors that will be described in the next section. There are also two optional functions in the debugmalloc.c file that you can implement:
void PrintAllocatedBlocks(); int HeapCheck();
PrintAllocatedBlocks should print out information about all currently allocated blocks. HeapCheck should check all the blocks for possible memory overwrites.
Implementation Details
To catch the errors, you will allocate a slightly larger amount of space and insert a header and a footer around the "requested payload". MyMalloc() will insert information into this area, and MyFree() will check to see if the information has not changed. The organization of the complete memory block is as shown below:
Header
|
Payload |
Footer
|
Note: MyMalloc() returns a pointer to the payload, not the beginning of the whole block. Also, the ptr parameter passed into MyFree(void *ptr) will point to the payload, not the beginning of the block. Information that you might want to store in this extra (header, footer) area include:
- a "fence" immediately around the requested payload with a known value like 0xCCDEADCC, so that you can check if it has been changed when the block is freed.
- the size of the block
- a checksum for the header to ensure that it has not been corrupted (A checksum of a sequence of bits is calculated by counting the number of "1" bits in the stream. For example, the checksum for "1000100010001000" is 4. It is a simple error detection mechanism.)
- the filename and line number of the MALLOC() call
The errors that can occur are:
- Error #1: Writing past the beginning of the user's block (through the fence)
- Error #2: Writing past the end of the user's block (through the fence)
- Error #3: Corrupting the header information
- Error #4: Attempting to free an unallocated or already-freed block
- Error #5: Memory leak detection (user can use ALLOCATEDSIZE to check for leaks at the end of the program)
To report the first four errors, call one of these two functions:
void error(int errorcode, char *filename, int linenumber);errorcode is the number assigned to the error as stated above. filename and linenumber contain the filename and line number of the line (the free call) in which the error is invoked. For example, call error(2, filename, linenumber) if you come across a situation where the footer fence has been changed.void errorfl(int errorcode, char *filename_malloc, int linenumber_malloc, char *filename_free, int linenumber_free);This is the same as the error() , except there are two sets of filenames and line numbers, one for the statement in which the block was malloc'd, and the other for the statement in which the block was free'd (and the error was invoked).
The fact that MyMalloc() and MyFree() are given the filename and line number of the MALLOC() and FREE() call can prove to be very useful when you are reporting errors. The more information you print out, the easier it will be for the programmer to locate the error. Use errorfl() instead of error() whenever possible. errorfl() obviously cannot be used on situations where FREE() is called on an unallocated block, since it was not ever MALLOC 'd.
Note: You will only be reporting errors from MyFree() . None of the errors can be caught in MyMalloc()
In the case of memory leaks, the driver program will call AllocatedSize() , and the grader will look at its return value and possible output. AllocatedSize() should return the number of bytes currently allocated from MALLOC and FREE calls. For example, the code segment:
void *ptr1 = MALLOC(10), *ptr2 = MALLOC(8); FREE(ptr2); printf("%d\n", AllocatedSize());
should print out "10". Once you have gotten to the point where you can catch all of the errors, you can go an optional step further and create a global list of allocated blocks. This will allow you to perform analysis of memory leaks and currently allocated memory. You can implement the void PrintAllocatedBlocks() function, which prints out the filename and line number where all currently allocated blocks were MALLOC() 'd. A macro is provided for you to use to print out information about a single block in a readable and gradeable format:
PRINTBLOCK(int size, char *filename, int linenumber)
Also, you can implement the int HeapCheck() function. This should check all of the currently allocated blocks and return -1 if there is an error and 0 if all blocks are valid. In addition, it should print out the information about all of the corrupted blocks, using the macro #define PRINTERROR(int errorcode, char *filename, int linenumber) , with errorcode equal to the error number (according to the list described earlier) the block has gone through. You may find that this global list can also allow you to be more specific in your error messages, as it is otherwise difficult to determine the difference between an overwrite of a non-payload area and an attempted FREE() of an unallocated block.
Evaluation
You are given 7 test cases to work with, plus 1 extra for testing a global list. You can type "debugmalloc -t n " to run the n -th test. You can see the code that is being run in driver.c. If you have Perl installed on your machine, use grader.pl to run all the tests and print out a table of results. There are a total of 100 possible points. Here is a rundown of the test cases and desired output (do not worry about the path of the filename):
Code |
char *str = (char *) MALLOC(12); strcpy(str, "123456789"); FREE(str); printf("Size: %d\n", AllocatedSize()); PrintAllocatedBlocks(); |
Error # | None |
Correct Output |
Size: 0 |
Points worth | 10 |
Details | 10 points for not reporting an error and returning 0 in
AllocatedSize()
|
Code |
char *str = (char *) MALLOC(8); strcpy(str, "12345678"); FREE(str); |
Error # | 2 |
Correct Output |
Error: Ending edge of the payload has been overwritten. in block allocated at driver.c, line 26 and freed at driver.c, line 28 |
Points worth | 15 |
Details | 6 pts for catching error 3 pts for printing the filename/line numbers 6 pts for correct error message |
Code |
char *str = (char *) MALLOC(2); strcpy(str, "12"); FREE(str); |
Error # | 2 |
Correct Output |
Error: Ending edge of the payload has been overwritten. in block allocated at driver.c, line 33 and freed at driver.c, line 35 |
Points worth | 15 |
Details | 6 pts for catching error 3 pts for printing the filename/line numbers 6 pts for correct error message |
Code |
void *ptr = MALLOC(4), *ptr2 = MALLOC(6); FREE(ptr); printf("Size: %d\n", AllocatedSize()); PrintAllocatedBlocks(); |
Error # | None |
Correct Output |
Size: 6 Currently allocated blocks: 6 bytes, created at driver.c, line 39 |
Points worth | 15 |
Details | 15 pts for not reporting an error and returning 6 from AllocatedSize Extra for printing out the extra block |
Code |
void *ptr = MALLOC(4); FREE(ptr); FREE(ptr); |
Error # | 4 |
Correct Output |
Error: Attempting to free an unallocated block. in block freed at driver.c, line 48 |
Points worth | 15 |
Details | 15 pts for catching error Extra for correct error message |
Code |
char *ptr = (char *) MALLOC(4); *((int *) (ptr - 8)) = 8 + (1 << 31); FREE(ptr); |
Error # | 1 or 3 |
Correct Output |
Error: Header has been corrupted.or Error: Starting edge of the payload has been overwritten. in block allocated at driver.c, line 52 and freed at driver.c, line 54 |
Points worth | 15 |
Details | 9 pts for catching error 6 pts for a correct error message |
Code |
char ptr[5]; FREE(ptr); |
Error # | 4 |
Correct Output |
Error: Attempting to free an unallocated block. in block freed at driver.c, line 59 |
Points worth | 15 |
Details | 15 pts for recognizing error Extra for printing correct error message |
Code |
int i; int *intptr = (int *) MALLOC(6); char *str = (char *) MALLOC(12); for(i = 0; i < 6; i++) { intptr[i] = i; } if (HeapCheck() == -1) { printf("\nCaught Errors\n"); } |
Error # | None |
Correct Output |
Error: Ending edge of the payload has been overwritten. Invalid block created at driver.c, line 64 Caught Errors |
Points worth | Extra |
Details | "Caught Errors" indicates that the HeapCheck() function worked correctly. Extra points possible. |
Your instructor may give you extra credit for implementing a global list and the PrintAllocatedBlocks() and HeapCheck() functions.
个人感觉比较郁闷,我的电脑没有windows系统。无赖之下,我将project中的部分文件修改了一下,然后在Ubuntu下完全通过了 ,Windows下没有测试 。
最后发现自己写多了,我写了一个链表来存储所有的错误,不过好像所有的测试都只有一个错误。
- debugging_malloc.zip (17.3 KB)
- 下载次数: 70
- Exercise03.zip (40.1 KB)
- 描述: 我的解答 注意整个测试环境是Ubuntu8.04+Gcc+Gdb
- 下载次数: 157
评论
Total Score: 75/100
* Debugging malloc
Score: 75/100
o Detailed Feedback
Score: 75/100
有很多语法错误,程序不能运行.
发表评论
-
Ruby 2.1 GC策略
2014-01-23 11:30 883对象管理主要涉及: Profiling support ... -
Google 持续集成介绍
2014-01-23 11:26 1495见附件PPT. 具体方案 构建描述 依赖分析 ... -
函数式编程 读后感
2013-12-30 15:24 1388一篇比较不错的文章: http://coolshel ... -
系统模块集成管理与版本控制学习
2013-12-27 12:01 1248论软件生命周期集成 http://www.infoq.com ... -
Ruby 动态特性鉴赏
2013-12-26 16:47 1265以下代码与代码学习来自<Ruby Best Prac ... -
Android应用插件化与动态部署 学习
2013-12-26 16:45 0通过REST将相关服务有语义的组合起来。 动态部署: ... -
用Markdown做文档的问题
2013-12-23 18:06 794一直有想一种语言能够解决文档编写问题。 一般文档编写 ... -
Android组件、通信与安全机制学习
2013-12-20 12:26 0现有问题: Android的组件间通信有哪些方法?其中的I ... -
Android root 原理学习
2013-12-15 23:51 2243学习资源: http://www.zhihu.com/qu ... -
global + Ruby
2012-11-16 13:07 1225http://simple-and-basic.com/200 ... -
Linux pthread线程同步相关的API学习
2012-11-12 18:43 1390原因 最近在深入理解Dalvik虚拟机的内部线程控制体系,其 ... -
MMTk代码学习(系统结构与流程)
2012-11-06 19:08 1590MMTk的整体结构和驱动模型主要由Plan, Collecto ... -
MMTk代码学习(RVM接口)
2012-11-06 14:52 1502前导 MMTk被RVM整个封装在后端,主要调用接口是 org ... -
MMTk代码学习(整体结构)
2012-11-05 17:03 2397必要的整体模块 对于一个完整的内存管理工具,主要涉及: ... -
嵌入式Java虚拟机 GC特性一览
2012-10-31 15:53 1236嵌入式Java虚拟机列表来源:http://en.wikipe ... -
Memory Analysis Tool OQL 用例汇总及语法学习
2012-10-28 16:36 2078典型用例 获取所有对象: SELECT * FROM $ ... -
Memory Analysis Tool 使用相关材料整理
2012-10-28 10:47 1942利用MAT分析问题 从转储(Dump)文件中调试并除错 ... -
手机设备操作系统架构图整理
2012-10-28 10:28 1453整体分析材料 Android,ChromeOS, WebO ... -
MMTk特性认识
2012-10-25 16:24 1687整体介绍 MMTk是一个内存管理的工具包 ,同时也是jik ... -
JavaScript V8 引擎相关资料
2012-10-25 14:54 1013V8 Javascript engine之所以快 针 ...
相关推荐
NULL 博文链接:https://qianjigui.iteye.com/blog/256678
我的解答 博文链接:https://qianjigui.iteye.com/blog/293416
NULL 博文链接:https://qianjigui.iteye.com/blog/285055
我的解答 博文链接:https://qianjigui.iteye.com/blog/255421
NULL 博文链接:https://qianjigui.iteye.com/blog/269501
样例程序和Microsoft Calendar Control 10.0 博文链接:https://qianjigui.iteye.com/blog/280667
这是我的解答 博文链接:https://qianjigui.iteye.com/blog/248917
我的解答 博文链接:https://qianjigui.iteye.com/blog/279144
我的解答 博文链接:https://qianjigui.iteye.com/blog/248918
我的解答 博文链接:https://qianjigui.iteye.com/blog/286506
我的解答 博文链接:https://qianjigui.iteye.com/blog/280249