Originally Posted by nobody
Would be nice to post to us the (at least) the whole failing log, so we can get the grasp of the problem. The ideal case should be to see the script you are using (I expect you use bash shell script for packaging).
In such the case GDB is not the best tool to be used (rather for C applications/user space C code, compiled with option -g/debug info/symbol table to be embedded into .exe code).
Yeah I think you misunderstood me - the packaging process was not not failing, the build was not failing and the rpm, srpm and debuginfo packages were all being spat out. The problem was that the resultant package was just not working, the package in question was actually a plugin for another application; one that was not spitting out any meaningful debug information beyond the name of the C++ method that it was faltering on.
So yes a debugger would have been the best option, the binary in question was being compiled with the debug symbols and I had installed the resultant debuginfo package. I never did get it working though it just spat out random characters. I have never used gdb before and would have liked to figure it out.
In the end I attached strace and pinpointed the source of the problem to the build not having access to the OpenGL header files and for some reason the build was succeeding anyway.
I have it all working now though.