[mythtv] Debugging mythtv?
Drew Bernat
abernat at zathras.net
Wed Jan 29 03:51:35 EST 2003
Does the installation process run 'strip' at any point? That explicitly
goes through and removes debugging symbols.
<rant>
Stripped binaries are _really really really_ annoying when trying to write
a debugger. So is -fomit-frame-pointer, which makes it nearly impossible
to get a good trace
</rant>
Compiling with -ggdb (or -g) and making sure strip doesn't get run should
do it.
Drew
On Wed, 29 Jan 2003, Ainsley McCall wrote:
> Hi, I noticed today that a few folks were talking about using DDD to debug
> mythtv 0.7.
> I tried this last week with mixed results. GDB always complains that it
> cannot find any debugging symbols. I tried to explicitly force them into
> the compile by writing a perl script to add the -ggdb flag to every gcc and
> g++ in the tree makefiles. It appears as though this is working, but still
> no symbols. I presume that there was some other optimization flag that was
> taking precedence over my hacked-in flag to add debugging symbols, or they
> were getting linked out later. There's gotta be a better way to do this.
>
> Perhaps I'm debugging the wrong executable. Should my command line be
> something other than `gdb mythtv` or `ddd mythfrontend`?
>
> Anyone have a quick tip on getting this to go?
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-dev
>
--
Drew Bernat __ ____
abernat at zathras.net | | |
http://www.zathras.net | |
More information about the mythtv-dev
mailing list