)]}' { "log": [ { "commit": "ac81fe8657119c265edcc2f05b3e5b7c5b17ae9f", "tree": "99a6e825926829bb7c8d955cbc96ae1777691ef9", "parents": [ "8945d5e43a25737f3f888a90742cc918b1124a05" ], "author": { "name": "Tamas Berghammer", "email": "tberghammer@google.com", "time": "Fri Aug 26 15:54:59 2016 +0100" }, "committer": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Thu Nov 17 13:13:27 2016 -0800" }, "message": "Enable malloc debug using environment variables\n\nPreviously malloc debug can be enabled only using global settings\naccessible to the root user only. This CL adds a new option to enable\nit using environment variables making it possible to use it with pure\nnative (shell) applications on production builds (from shell user) and\nprepares it for using it from logwrapper on production devices.\n\nRemove the old environment variable and property since they are not\nnecessary.\n\nTest: Enable malloc debug using environment variable and verify\nTest: that it only affects the commands launched from the shell.\nTest: Enable malloc debug using the property variable and verify\nTest: that it affects all commands.\nTest: Run all unit tests in 32 bit and 64 bit.\nChange-Id: Iecb75a3471552f619f196ad550c5f41fcd9ce8e5\n" }, { "commit": "545808a60875868d5cc5226024440679590bb808", "tree": "c6a120ff56cdee0e20c80e8750679f9a4b86c598", "parents": [ "42d24ca8188fac3ba96a1b9a482924658668973b" ], "author": { "name": "Tamas Berghammer", "email": "tberghammer@google.com", "time": "Fri Aug 26 12:34:16 2016 +0100" }, "committer": { "name": "Tamas Berghammer", "email": "tberghammer@google.com", "time": "Fri Aug 26 12:34:16 2016 +0100" }, "message": "Fix a typo in the debug malloc usage info\n\nChange-Id: I010fdc6c228a5f64edfef1c267cde7a2eef5190b\n" }, { "commit": "7bd01783a830f72c1245c262a7fd9a199e90aed1", "tree": "5bd657e6c452d5f9d81a6c9b156ee748c8a8f070", "parents": [ "a0e205e3b4f7993affb864260e924ce9f20573d0" ], "author": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Wed Apr 20 12:30:58 2016 -0700" }, "committer": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Fri Jul 08 14:05:17 2016 -0700" }, "message": "Add the record alloc option.\n\nThis option adds the ability to record all of the allocation requests\nand dump them to a file when a signal is sent to the process.\n\nIncluded in this change, redo the option processing to add a new\nstring option.\n\nBug: 27747898\n\nChange-Id: Ida043362e38b5eb1d459c99db9c2581015dab366\n" }, { "commit": "62e3a078aa7b156139b1a2cec77e1a84eb10c5a4", "tree": "b37425943e0cd7284b319d6cad98bd71dcfdc8bb", "parents": [ "9ee905f12fa0aeb4ae0df708e15d2ffcfaf58000" ], "author": { "name": "Chih-Hung Hsieh", "email": "chh@google.com", "time": "Tue May 03 12:08:05 2016 -0700" }, "committer": { "name": "Chih-Hung Hsieh", "email": "chh@google.com", "time": "Tue May 03 12:08:05 2016 -0700" }, "message": "Fix google-explicit-constructor warnings.\n\nBug: 28341362\nChange-Id: I84effbdfa1b9b39328a909b7f70fe17e7ee316c8\n" }, { "commit": "ea26b33248663a836d2f0719cb4e46967b648fe2", "tree": "30c13529fed73bab313373ba3ad5a10c9795ced8", "parents": [ "668fddb3ba36b52a16381513b1a0a42d9dd910e1" ], "author": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Fri Apr 15 14:13:52 2016 -0700" }, "committer": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Fri Apr 15 14:13:52 2016 -0700" }, "message": "Small fixes to malloc debug.\n\n- Change the printed name from pointer to allocation to be explicit about\n what is wrong.\n- Change the signal to be SIGRTMAX - 19 instead of SIGRTMIN. This should\n prevent problems if we have to reserve other real time signals.\n\nBug: 28218530\nChange-Id: Ic7d9c471929264d8e47bafaffc16e099840c9e71\n" }, { "commit": "a4b14252752d14454afb48feb3272e8689e3a66d", "tree": "939fc4e7324147dd97d0e54d9383bb1758ec8848", "parents": [ "0e00c168cea9c951df5ce47d25d8f042b9cc566a" ], "author": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Mon Mar 14 15:29:46 2016 -0700" }, "committer": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Mon Mar 14 15:34:22 2016 -0700" }, "message": "Fix problem where unknown option is not an error.\n\nIf the first option is found, then any unknown options are simply\nignored, but do not produce an error. Fixed this so that each\noption found is actually verified to exist.\n\nBug: 27620263\nChange-Id: If58732df3285eeae72188162c505e0e202fada8c\n" }, { "commit": "549e52200b6af3c33cba7ef759ea98b49fa40082", "tree": "bf86a923f9e99668414f03f47b41f5493ef33072", "parents": [ "eb727252f22bd533ebfd40637c0718fdc9946221" ], "author": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Mon Feb 22 19:23:26 2016 -0800" }, "committer": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Fri Feb 26 17:02:17 2016 -0800" }, "message": "Move hard-coded values to constants.\n\nChange all of the hard-coded config values to be defined constants.\nAlso make sure to use these constants in the usage output.\n\nBug: 26739265\nChange-Id: I597a6d71279a2df9cc7e98c42ac70224261bac99\n" }, { "commit": "72df6708c829a4c6494936fdfbda6dc7e68e647b", "tree": "17ede0d54b6f50c3598a3fcec56f50754067690d", "parents": [ "72bca4b4105e24058f3f2eca024382bedb122a30" ], "author": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Thu Feb 11 15:51:31 2016 -0800" }, "committer": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Fri Feb 12 17:30:30 2016 -0800" }, "message": "Fix the default alignment of the allocations.\n\nIn order to enforce this constraint:\n\nThe pointer returned if the allocation succeeds shall be suitably\naligned so that it may be assigned to a pointer to any type of object\nand then used to access such an object in the space allocated.\n\nForce all allocations on 32 bit systems to have 8 byte alignment,\nand all allocations on 64 bit systems to have 16 byte alignment.\n\nAdd a test to verify that the allocator returns the correct alignments.\n\nBug: 26739265\nChange-Id: I9af53279617408676b94e4ec6481b3ed7ffafc6a\n" }, { "commit": "7993b80f894db20af4d1d154221c42fea6171a3d", "tree": "fc99d36000a8f0853224d75296d96509a730ee05", "parents": [ "50647711ebaf2360aca05cc94a2fdf431c1a153e" ], "author": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Thu Jan 28 18:35:05 2016 -0800" }, "committer": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Fri Jan 29 15:19:22 2016 -0800" }, "message": "Add better free tracking.\n\nIncluded in this change:\n\n- Change the tag when a pointer is freed so it\u0027s easy to detect if\n an already freed pointer is being used.\n- Move the free backtrace out of the header. This backtrace is only\n used under only some circumstances, so no need to allocate space\n in all headers for it.\n- Add new option free_track_backtrace_num_frames to specify how many\n frames to record when the free occurs. This removes the dependency\n on the backtrace option to get backtraces.\n\nBug: 26739265\nChange-Id: I76f5209507dcf46af67ada162a7cb2bf282116f2\n" }, { "commit": "166c8535a5a4253bcb2b04bbd20a2a8c04c44f2c", "tree": "09ea8c0e5618aaee0434ad89b83c5ae05162642a", "parents": [ "e4daf100b33fb17936b4d61e0ddfe679fcd04123" ], "author": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Wed Jan 27 17:23:36 2016 -0800" }, "committer": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Wed Jan 27 18:13:09 2016 -0800" }, "message": "Add min/max values for config values.\n\nThis is to only allow realistic values for some of the options.\n\nBug: 26739265\n\nChange-Id: I172d5401c27e5d638d80f1c93c678c26c4dae0fc\n" }, { "commit": "f2b67b85f5e192812212d3176c07e195c0ffa503", "tree": "e2630c9e80cd0fa29601c63272663842a5a12e9c", "parents": [ "63860cb8fd1adf3f679b9b4ad876323a8d65cd9d" ], "author": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Mon Jan 25 14:36:34 2016 -0800" }, "committer": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Mon Jan 25 14:36:34 2016 -0800" }, "message": "Fix build for gcc.\n\nGcc doesn\u0027t like the brace object initialization, so make all of\nthe Feature objects explicit.\n\nAlso, no arguments to the error_log macros make gcc unhappy, so add\nan option to turn these into warnings. These will be fixed when we\nadd the explicit _error and _warn log functions.\n\nChange-Id: I35af834dabb5548923e893dd980a751fdebfa13a\n" }, { "commit": "63860cb8fd1adf3f679b9b4ad876323a8d65cd9d", "tree": "25aeae686d92efcb5e08a54e8cba1e8c31efe33b", "parents": [ "ad9c3f34f762ed45cce5dbb93218124ed31f6873" ], "author": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Mon Nov 16 17:30:32 2015 -0800" }, "committer": { "name": "Christopher Ferris", "email": "cferris@google.com", "time": "Mon Jan 25 10:54:21 2016 -0800" }, "message": "Malloc debug rewrite.\n\nThe major components of the rewrite:\n\n- Completely remove the qemu shared library code. Nobody was using it\n and it appears to have broken at some point.\n- Adds the ability to enable/disable different options independently.\n- Adds a new option that can enable the backtrace on alloc/free when\n a process gets a specific signal.\n- Adds a new way to enable malloc debug. If a special property is\n set, and the process has an environment variable set, then debug\n malloc will be enabled. This allows something that might be\n a derivative of app_process to be started with an environment variable\n being enabled.\n- get_malloc_leak_info() used to return one element for each pointer that\n had the exact same backtrace. The new version returns information for\n every one of the pointers with same backtrace. It turns out ddms already\n automatically coalesces these, so the old method simply hid the fact\n that there where multiple pointers with the same amount of backtrace.\n- Moved all of the malloc debug specific code into the library.\n Nothing related to the malloc debug data structures remains in libc.\n- Removed the calls to the debug malloc cleanup routine. Instead, I\n added an atexit call with the debug malloc cleanup routine. This gets\n around most problems related to the timing of doing the cleanup.\n\nThe new properties and environment variables:\n\nlibc.debug.malloc.options\n Set by option name (such as \"backtrace\"). Setting this to a bad value\n will cause a usage statement to be printed to the log.\n\nlibc.debug.malloc.program\n Same as before. If this is set, then only the program named will\n be launched with malloc debug enabled. This is not a complete match,\n but if any part of the property is in the program name, malloc debug is\n enabled.\n\nlibc.debug.malloc.env_enabled\n If set, then malloc debug is only enabled if the running process has the\n environment variable LIBC_DEBUG_MALLOC_ENABLE set.\n\nBug: 19145921\n\nChange-Id: I7b0e58cc85cc6d4118173fe1f8627a391b64c0d7\n" } ] }