Here's a quick and easy solution
on
Memory Leaks
·
· Score: 2, Informative
Write a malloc wrapper and #define it in place of the real thing. With #define you can easily log the location in the code, amount of RAM, and location in memory to a file, then write a script in the language of your choice to see which locations in RAM weren't dealloced, and match them with the appropriate malloc call, which also contains the location in code. It took me about an hour to implement this in a multi-thousand line program and it works very well. The only thing it doesn't catch is when a library call mallocs something and expects you to dealloc it, but i solved this by including a fake malloc call that just logs but doesn't actually malloc, so you'd call it right after the library call that actually does the malloc.
I looked around on sourceforge a little, and found several group-collaboration web interfaces using PHP, perl, etc. Here is a link to Office-Business/Scheduling at sourceforge. If you're thinking about group-oriented things, some things there look pretty good, and you could access them with lynx.
As for PalmOS, there are some console-based apps that interface with the Palm. I don't know how functional they are, but I assume you could find one that uses a standard format like iCal. This could then be combined with a web interface or whatever else you can find.
My guess though, just from looking around, is that you'll have to separate the Palm synching from the scheduling app, I couldn't find a decently funtional console app that also syncs with Palm.
One last thing: why no GUI? I know what some say about the console-GUI debate, but it seems to me that there is just more you can put in a GUI interface.
I have not had this problem with WP, but I have with other precompiled binaries. The problem is one or both of 2 things:
1: You have the libraries it needs, but they are the wrong version.
2: You don't have the libraries it needs
Simple enough so far? Good.
Now use the ldd util. to see which libraries the binaries need (ie what they are linked to). For example:
$ ldd wpinstc
This outputs a list telling what libraries it is linked to, and what they point to on your system, or "missing" if they are missing. So see what libraries are missing.
Most likely, there will be a library marked missing, called "something.so.version". This name.so.version is a symlink to the real library, name.so.
Why? To prevent incompatibilities caused by linking to a library that is too new or too old. The version in the symlink is the version of the actual library, so binaries are linked to the symlinks instead of the actual library. So when you don't have the version it "needs", it doesn't work.
BUT you probably have a newer version of the library, in which case it will probably be okay. Even if you have an older version, it's worth a try. To fool the linker, make a symlink from whatever name it says it needs to the actual library, in the same directory as the library (usually/lib,/usr/lib, or/usr/local/lib). Then run ldconfig to examine the new stuff. Now run the binary and see if it works.
One last thing if it doesn't work: ldconfig may remove the symlink you make, so see if anything happened to it when you ran ldconfig, and if it's gone make it again and don't run ldconfig.
Also, the problem may just be a bad symlink, ie a symlink that points to a nonexistant file. Or sometimes just running ldconfig helps:-)
True UNIX is just a label. Look at the structure of the OS. I'm not an expert or anything but OSX uses the UNIX security model, not the bloated NT model. (Which by the way MS said was superior to UNIX's and then came the IIS root exploit stemming from overly-complicated security model).
Look at the locking mechanisms, driver philosophy, programming philosophy.
They got XF4 running on OSX pretty quick--it compiles with no user hacking.
I'm glad Apple is finally releasing a decent OS after the MacOS's through nine which internally were level with DOS and Win3.1. After seeing Win for what it really was and choosing a new OS (I chose Linux) I've also seen that MacOS is not a bad thing! Maybe OSX can put some serious pressure on M$!
Doesn't PGP stand for Pretty Good Privacy? (That's not a joke or anything, is it?). If someone wanted to give someone something extremely confidential, would they e-mail it encrypted? No, they would either give it to them personally or get some trusted person to do it.
No encryption is perfect, and is only secure when used for what it's designed for. PGP is good for what it's designed for.
BTW, about the key being as secure as the comp it's stored on, wouldn't the key be on the same machine the thing being encrypted is on? Anyway that's my two cents.
Jeez! Don't be so cynical. What makes you think that out of how-ever-many people submitted an article like this, they should post yours?! If all you're gonna do is bash/., send your packets somewhere else like msn.com.
I'm sorry, but Windows is beyond rescuing. If Micro$oft had any sense at all, they'd rewrite the whole thing and give it a new name. I don't really care though; I dumped M$oft about a year ago. PS as if a lightning strike from Gates, IE (had no choice, I'm at school now) just crashed randomly as I was typing this the first attempt.
Slashdot Mirror
Write a malloc wrapper and #define it in place of the real thing. With #define you can easily log the location in the code, amount of RAM, and location in memory to a file, then write a script in the language of your choice to see which locations in RAM weren't dealloced, and match them with the appropriate malloc call, which also contains the location in code. It took me about an hour to implement this in a multi-thousand line program and it works very well. The only thing it doesn't catch is when a library call mallocs something and expects you to dealloc it, but i solved this by including a fake malloc call that just logs but doesn't actually malloc, so you'd call it right after the library call that actually does the malloc.
Yes i'm burning a karma point for offtopic just to say this is the kind of stuff that induces suicides...
I looked around on sourceforge a little, and found several group-collaboration web interfaces using PHP, perl, etc. Here is a link to Office-Business/Scheduling at sourceforge. If you're thinking about group-oriented things, some things there look pretty good, and you could access them with lynx.
As for PalmOS, there are some console-based apps that interface with the Palm. I don't know how functional they are, but I assume you could find one that uses a standard format like iCal. This could then be combined with a web interface or whatever else you can find.
My guess though, just from looking around, is that you'll have to separate the Palm synching from the scheduling app, I couldn't find a decently funtional console app that also syncs with Palm.
One last thing: why no GUI? I know what some say about the console-GUI debate, but it seems to me that there is just more you can put in a GUI interface.
I have not had this problem with WP, but I have with other precompiled binaries. The problem is one or both of 2 things:
1: You have the libraries it needs, but they are the wrong version.
2: You don't have the libraries it needs
Simple enough so far? Good.
Now use the ldd util. to see which libraries the binaries need (ie what they are linked to). For example:
$ ldd wpinstc
This outputs a list telling what libraries it is linked to, and what they point to on your system, or "missing" if they are missing. So see what libraries are missing.
Most likely, there will be a library marked missing, called "something.so.version". This name.so.version is a symlink to the real library, name.so.
Why? To prevent incompatibilities caused by linking to a library that is too new or too old. The version in the symlink is the version of the actual library, so binaries are linked to the symlinks instead of the actual library. So when you don't have the version it "needs", it doesn't work.
BUT you probably have a newer version of the library, in which case it will probably be okay. Even if you have an older version, it's worth a try. To fool the linker, make a symlink from whatever name it says it needs to the actual library, in the same directory as the library (usually /lib, /usr/lib, or /usr/local/lib). Then run ldconfig to examine the new stuff. Now run the binary and see if it works.
One last thing if it doesn't work: ldconfig may remove the symlink you make, so see if anything happened to it when you ran ldconfig, and if it's gone make it again and don't run ldconfig.
Also, the problem may just be a bad symlink, ie a symlink that points to a nonexistant file. Or sometimes just running ldconfig helps :-)
Good luck, tell me if it works! :-)
True UNIX is just a label. Look at the structure of the OS. I'm not an expert or anything but OSX uses the UNIX security model, not the bloated NT model. (Which by the way MS said was superior to UNIX's and then came the IIS root exploit stemming from overly-complicated security model). Look at the locking mechanisms, driver philosophy, programming philosophy.
They got XF4 running on OSX pretty quick--it compiles with no user hacking.
I'm glad Apple is finally releasing a decent OS after the MacOS's through nine which internally were level with DOS and Win3.1. After seeing Win for what it really was and choosing a new OS (I chose Linux) I've also seen that MacOS is not a bad thing! Maybe OSX can put some serious pressure on M$!
If I were a CEO or something, I wouldn't be spending money on VR video conferencing. I would rather play some cool-ass VR hack on Unreal or Q3.
Doesn't PGP stand for Pretty Good Privacy? (That's not a joke or anything, is it?). If someone wanted to give someone something extremely confidential, would they e-mail it encrypted? No, they would either give it to them personally or get some trusted person to do it.
No encryption is perfect, and is only secure when used for what it's designed for. PGP is good for what it's designed for.
BTW, about the key being as secure as the comp it's stored on, wouldn't the key be on the same machine the thing being encrypted is on? Anyway that's my two cents.
I get it! Thanks! No wonder stability didn't quite feel right when I just grabbed the latest of each package. :-)
Jeez! Don't be so cynical. What makes you think that out of how-ever-many people submitted an article like this, they should post yours?! If all you're gonna do is bash /., send your packets somewhere else like msn.com.
I'm sorry, but Windows is beyond rescuing. If Micro$oft had any sense at all, they'd rewrite the whole thing and give it a new name. I don't really care though; I dumped M$oft about a year ago. PS as if a lightning strike from Gates, IE (had no choice, I'm at school now) just crashed randomly as I was typing this the first attempt.