https://sourceware.org/bugzilla/show_bug.cgi?id=31009
--- Comment #9 from Jonny Weir <jonny.weir at clearpool dot io> --- Hi Nick (In reply to Nick Clifton from comment #8) > Hi Jonny, > > (In reply to Jonny Weir from comment #3) > > > > Are you able to attach a debugger to the linker and discover the values > > > that > > > are triggering this assertion ? The code looks like this: > > > > I attached gdb to the ld process, but I think a few things happen that make > > it more difficult to get a stack trace. I believe it forks another process > > and that is the process that spits out the assertion messages, so when that > > returns, there is no stack to examine. Unless there is a way to do this that > > I don't see, I cant see how to get the required stack trace. > > As you have already found, using printf()s in a situation like this is > generally the best way to proceed, but just in case you are interested it is > possible to run gdb on the actual link process, although it is rather > complicated: > > ... Many thanks for this detailed explanation! That is very useful and good to know. It's always great to expand the repertoire with a few more tools. -- You are receiving this mail because: You are on the CC list for the bug.
