Garbage output without cout, printf or another ...
When I run a program a lot of characters are showed at end of program execution, although i don't use any like cout or printf functions that could display variables.
This occurs when I execute program twice or more times.
I'm using malloc and free to allocate a block of 60000 chars.
The code is here... At first post.
Some garbage is displayed also if I remove all printf functions...
Last edited by albert_sps; 03-22-2008 at 06:51 PM. Reason: More information about this issue
Ah yes, this must be solar rays from outer space affecting your your processor in such a manner that it prints characters to your screen. Nothing you can do about it really.
The above was an answer that was as useless as your question. When your car breaks down, do you go to a mechanic without your car, and ask him: "Hey, my car broke down. What's wrong with it?" He can't fix it without having the car or for that matter tell you what's wrong with it without taking a peek at the engine.
Where's your code?
Well, i'll get some GC library. Althougt use INT 21,4A to modify allocated memory block should help, theoretically....
Are we stuck in the stone age?
Mostly likely, a GC library won't help because you are using freed memory or have memory corruption somewhere or the like.
Garbage Collection libraries make sure you don't get leaks.
Originally Posted by Adak
Well looking at the code I see at least two very serious memory trashing opportunities.
> cmd[0] = (char) strlen(argv[3]);
And where is cmd pointing? - answer, nowhere in particular. Certainly not anywhere you can be sure is safe to write to.
> memset(par, 0, sizeof(par));
Frankly I'm amazed this compiled without warnings even on a crusty fossil compiler.
The first parameter should be &par
Who knows what you just filled with a bunch of zeros.
With such an old compiler, you really need to know what you're doing because it will generally compile anything which is syntactically valid regardless of how little sense it makes.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
GCC to the rescue
=========================================
Everytime you segfault, you murder some part of the world
Huh?
^ Salem dissed the compiler the OP used, so I recommended GCC
=========================================
Everytime you segfault, you murder some part of the world
Well... then, I must recommend Visual Studio. It is far better IMHO. Safe library, very powerful debugging facilities, so easy to install & use & configure, even the compiler itself. This assumes Windows, of course.
I couldn't get a single thing running on visual studio, it gave me linker errors. I can't be bothered to figure out linker errors when all I try to run is a simple hello world program, imagine the errors i'd get if I tried to run more complex programs.
=========================================
Everytime you segfault, you murder some part of the world
Pfft. You don't know what you're doing, that's all.
It's no different than any other linker. You get errors sometime.
And you can get errors if you choose the wrong project type, too.
