Hello,
On Mon, 26 Oct 2009, Rahul Sundaram wrote:
> In RPM based distributions, the build system generally creates a
> separate debug/debuginfo package that you can install to get the debug
> symbols rather than recompile anything.
... and later ...
> Debian and derivates don't do this yet but a
On Mon, Oct 26, 2009 at 12:14 PM, Varrun Ramani wrote:
> I did not understand what "debug symbols" is.Could you elucidate?
You have to get your e-mail quoting right while replying. ;)
Anyway don't get too worried about my language.
All I mean is that if you don't compile the code with
the -g o
On 10/26/2009 03:02 PM, Mehul Ved wrote:
> On Mon, Oct 26, 2009 at 12:14 PM, Varrun Ramani wrote:
>> 2009/10/26 Girish Venkatachalam
>>
>>>
>>> -g is for generating debug symbols so you can use the executable with
>>> gdb(1).
>>>
>>> I did not understand what "debug symbols" is.Could you elucidat
On Mon, Oct 26, 2009 at 12:14 PM, Varrun Ramani wrote:
> 2009/10/26 Girish Venkatachalam
>
>>
>> -g is for generating debug symbols so you can use the executable with
>> gdb(1).
>>
>> I did not understand what "debug symbols" is.Could you elucidate?
http://en.wikipedia.org/wiki/Debug_symbol
I h
2009/10/26 Girish Venkatachalam
>
> -g is for generating debug symbols so you can use the executable with
> gdb(1).
>
> I did not understand what "debug symbols" is.Could you elucidate?
> That is ensured by -g. Also the command strip(1) will remove debug symbols.
>
> The other thing you can do
I think the subject is self explanatory.
I am going to talk about two options of gcc.
-Wall is for warnings. Your code should compile without any warnings.
Throw away useless variables
or comment them out and do appropriate typecasting when you have
const char * and char * and similar.
-g is fo
