running watches best value image
Sunshine
I want to find out the value of any or all years of Merkur XR4Ti cars because I want to buy another one so where would I go to check this ? Does anyone know ? ......They are Fords that were made in Europe from 1985 through 1990 I believe.
Answer
They are getting pretty scarce and you don't see them for sale much anymore. They used to be pretty common and very cheap, but then they got discovered as a cheap hotrod with their IRS and turbocharged engine. Most of them have been scraped out, but some remain in stock or modified condition.
They do pop up on Ebay and craigslist from time to time. You just have to keep watching.
You might find a project for around $500 or even a nice one for $2-4K
They are listed in the Old Cars Price Guide magazine found at your bookstore. You should get one if you are serious about buying one. They start out at $240 for a #6 1985 and end at $15k for a #1 1989
Since it runs the same engine package as the SVO, try this group
http://autos.groups.yahoo.com/group/svoowners
Good luck
They are getting pretty scarce and you don't see them for sale much anymore. They used to be pretty common and very cheap, but then they got discovered as a cheap hotrod with their IRS and turbocharged engine. Most of them have been scraped out, but some remain in stock or modified condition.
They do pop up on Ebay and craigslist from time to time. You just have to keep watching.
You might find a project for around $500 or even a nice one for $2-4K
They are listed in the Old Cars Price Guide magazine found at your bookstore. You should get one if you are serious about buying one. They start out at $240 for a #6 1985 and end at $15k for a #1 1989
Since it runs the same engine package as the SVO, try this group
http://autos.groups.yahoo.com/group/svoowners
Good luck
I have written a program in Linux. It will run as a module. How can check for memory leaks in it?
sun
I thought about the following way,
1. Get system free memory
2. Load and the module (insmod)
3. Run it for a while and then remove it(rmmod)
4. Check the system free memory
5. Get the difference.
But I am not sure how effective this method will be, as other tasks will also be running and they will also allocate memory.
Answer
There are 3 main approaches I can think of,
1. Create a wrapper above kmalloc()/kfree() that keeps track of the memory located... maintaining the allocators' info and how many times kmalloc() has been called.
Decrement this value when kfree() is called. When your module is to exist, make sure that value is 0 (ie # kmallocs = # kfrees called).
2. Run your module as sortof a "program" -- very hard if the module is huge, and use a tool like valgrind to find memory leaks.
3. Watch /proc/meminfo and /proc/slabinfo to find memory leaks by hand... can be rather tedious (similar to your suggested method).
Have fun :)
There are 3 main approaches I can think of,
1. Create a wrapper above kmalloc()/kfree() that keeps track of the memory located... maintaining the allocators' info and how many times kmalloc() has been called.
Decrement this value when kfree() is called. When your module is to exist, make sure that value is 0 (ie # kmallocs = # kfrees called).
2. Run your module as sortof a "program" -- very hard if the module is huge, and use a tool like valgrind to find memory leaks.
3. Watch /proc/meminfo and /proc/slabinfo to find memory leaks by hand... can be rather tedious (similar to your suggested method).
Have fun :)
Powered by Yahoo! Answers
No comments:
Post a Comment