Re: Re: gdb does not stop at printf for ppc

On 11/4/25 10:00 PM, Sachin Monga wrote:
> I've tested the solution provided by Adhmerval and it worked well.
> No regressions found on test-suite also.

Excellent!



> Next, my question to the community is that do I need to create aliasing for
> all the symbols as in the list prepared by Carl as discussed in the thread ?
> 
> For now, I need urgent solution for printf specifically. So, Is it ok to
> proceed and share this change for printf only ?

I think it's fine to submit a patch for printf now and wait on the other
symbols later.  As Adhemerval mentioned, there are more symbols than just
the IEEE128 symbols that need fixing too, so this looks like it'll be a
multi-patch process to fix everything and I don't expect you to fix the
non-IEEE128 symbols.

That said, I think when fixing printf, we should fix the other printf like
functions at the same time, since they're related.  For example, fprintf,
etc.  There shouldn't be too many of those.

Peter