[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 03/11/10 12:22, tom wrote:
I should have added that compiling for debugging makes the damn thing work. It should be possible to generate a separate symbol file that the debugger can use to follow the code after a segfault rather than adding it to the executable. If I could work out what was happening in the program I'd write some unit tests...On 03/11/10 08:26, Simon Waters wrote:Its not my code and it uses some dynamic build method which makes it really hard to work out whats what! And apparently I'm looking for symbol files - gdb can take one but I cant see how to generate one...On 03/11/10 08:05, tom wrote:When I was a lad.... When one compiles for debug these days the exe file is not the same asthe running version that crashes hence the difficulty of finding certainproblems. I remember in my youth compiler/linkers making a separate map file that could be used by the debugger - can the gnu tools do this?Don't know, probably, but you can run add debugging to optimised code - the results are "interesting" at times but works well enough and usually finds problems caused by over optimistic optimisation. Although one wonders what sort of code you are feeding it to find bugs these days.... http://www.delorie.com/gnu/docs/gdb/gdb_17.htmlTom te tom te tom
Tom te tom te tom -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq