Re: [gentoo-user] posting a useful bug to bugzilla
On Monday 11 August 2003 15:40, daniel wrote: On Mon, 2003-08-11 at 09:23, Renat Golubchyk wrote: From /usr/portage/profiles/use.desc : --- cut here --- debug - Tells configure and the makefiles to build for debugging. Effects vary acrosss packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES+=nostrip too. --- cut here --- Set debug USE flag and add nostrip to FEATURES and you can do some debugging. just one last question: what does nostrip do? nostrip tells portage not to strip the binaries after compilation. The binaries remain bigger in size but they also have the symbols in them (like debugging symbols). After stripping the binaries become smaller, sometimes even 3 or 4 times smaller. Stripping is as far as I know safe, so nothing gets broken. See man strip. Cheers, Renat -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] posting a useful bug to bugzilla
On August 11, 2003 10:01 am, Renat Golubchyk wrote: nostrip tells portage not to strip the binaries after compilation. The binaries remain bigger in size but they also have the symbols in them (like debugging symbols). After stripping the binaries become smaller, sometimes even 3 or 4 times smaller. Stripping is as far as I know safe, so nothing gets broken. See man strip. you mentioned that this feature can enlarge a binary... does this mean i'll take a performance hit? i only ask 'cause if this is not the case, i'll recompile everything i have with these options... -- money never made a man happy yet, nor will it. there is nothing in its nature to produce happiness. the more a man has, the more he wants. instead of filling a vacuum, it makes one. - ben franklin -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] posting a useful bug to bugzilla
On Mon, Aug 11, 2003 at 06:42:35PM -0400, gabriel wrote: On August 11, 2003 10:01 am, Renat Golubchyk wrote: nostrip tells portage not to strip the binaries after compilation. The binaries remain bigger in size but they also have the symbols in them (like debugging symbols). After stripping the binaries become smaller, sometimes even 3 or 4 times smaller. Stripping is as far as I know safe, so nothing gets broken. See man strip. you mentioned that this feature can enlarge a binary... does this mean i'll take a performance hit? i only ask 'cause if this is not the case, i'll recompile everything i have with these options... No. The binary simply contains additional data that is used by debuggers so it will know where to find variables, functions, and map instruction addresses to file and line number (or the other way around), and things of that nature. The executable does not need any of this information, which is why it can be stripped. - PK -- money never made a man happy yet, nor will it. there is nothing in its nature to produce happiness. the more a man has, the more he wants. instead of filling a vacuum, it makes one. - ben franklin -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] posting a useful bug to bugzilla
On Monday 11 August 2003 13:54, gabriel wrote: the new version of kopete (0.7) while full of really cool features, doesn't work at all on my machine and continues to crash. so i filled out a bug report on bugs.kde.org. the problem is, i wasn't able to offer much information, even though i have gdb installed, the only messages i get are a long list of: (no debugging symbols found)... so the only response to my bug was: Please include -g in the flags if you want your backtrace to contain useful information. Using --enable-debug in configure as well is recommended. ...so how do i do this? is there a useflag to set? or a command line variable? or do i have to build kopete without portage? From /usr/portage/profiles/use.desc : --- cut here --- debug - Tells configure and the makefiles to build for debugging. Effects vary acrosss packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES+=nostrip too. --- cut here --- Set debug USE flag and add nostrip to FEATURES and you can do some debugging. Cheers, Renat -- [EMAIL PROTECTED] mailing list
[gentoo-user] posting a useful bug to bugzilla
the new version of kopete (0.7) while full of really cool features, doesn't work at all on my machine and continues to crash. so i filled out a bug report on bugs.kde.org. the problem is, i wasn't able to offer much information, even though i have gdb installed, the only messages i get are a long list of: (no debugging symbols found)... so the only response to my bug was: Please include -g in the flags if you want your backtrace to contain useful information. Using --enable-debug in configure as well is recommended. ...so how do i do this? is there a useflag to set? or a command line variable? or do i have to build kopete without portage? -- the world needs dreamers and the world needs doers. but above all, the world needs dreamers who do. - sarah ban breathnach -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] posting a useful bug to bugzilla
On Mon, 2003-08-11 at 09:23, Renat Golubchyk wrote: From /usr/portage/profiles/use.desc : --- cut here --- debug - Tells configure and the makefiles to build for debugging. Effects vary acrosss packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES+=nostrip too. --- cut here --- Set debug USE flag and add nostrip to FEATURES and you can do some debugging. just one last question: what does nostrip do? -- the great only appear great because we are on our knees - james connolly -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] posting a useful bug to bugzilla
On August 11, 2003 07:33 pm, Bryan Feir wrote: On Mon, Aug 11, 2003 at 04:14:23PM -0700, Pat Kerwan wrote: On Mon, Aug 11, 2003 at 06:42:35PM -0400, gabriel wrote: you mentioned that this feature can enlarge a binary... does this mean i'll take a performance hit? i only ask 'cause if this is not the case, i'll recompile everything i have with these options... No. The binary simply contains additional data that is used by debuggers so it will know where to find variables, functions, and map instruction addresses to file and line number (or the other way around), and things of that nature. And more to the point, said information is not even loaded into memory unless you have a debugger running on the program; it only takes up space on the disk, not in RAM. So aside from a possible but tiny increase in load time, it won't affect performance at all. alright then, i've permanently added the above to my make.conf file. but recompiling kopete with these changes provided me no new information after the crash. ie. before i recompiled, i got the following after a crash: (no debugging symbols found)...(no debugging symbols found)... ...many times (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 5979)] 0x4162af67 in waitpid () from /lib/libpthread.so.0 #0 0x4162af67 in waitpid () from /lib/libpthread.so.0 now i just get this: [New Thread 16384 (LWP 6945)] 0x41632f67 in waitpid () from /lib/libpthread.so.0 #0 0x41632f67 in waitpid () from /lib/libpthread.so.0 how is the second version any more helpful than the first? -- mr. ghandi, what do you think of western civilization? i think it would be a good idea. - reporter to mahatma ghandi -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] posting a useful bug to bugzilla
On Mon, 2003-08-11 at 08:23, Renat Golubchyk wrote: On Monday 11 August 2003 13:54, gabriel wrote: the new version of kopete (0.7) while full of really cool features, doesn't work at all on my machine and continues to crash. so i filled out a bug report on bugs.kde.org. the problem is, i wasn't able to offer much information, even though i have gdb installed, the only messages i get are a long list of: (no debugging symbols found)... so the only response to my bug was: Please include -g in the flags if you want your backtrace to contain useful information. Using --enable-debug in configure as well is recommended. ...so how do i do this? is there a useflag to set? or a command line variable? or do i have to build kopete without portage? From /usr/portage/profiles/use.desc : --- cut here --- debug - Tells configure and the makefiles to build for debugging. Effects vary acrosss packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES+=nostrip too. --- cut here --- Set debug USE flag and add nostrip to FEATURES and you can do some debugging. Also, don't -fomit-frame-pointers. signature.asc Description: This is a digitally signed message part
