------- Comment #8 from ebotcazou at gcc dot gnu dot org 2006-01-17 08:47 ------- > You're assuming hex_to_chararacter is 'entered' normally. It is NOT. The > corrupt stack causes a branch into the middle of that routine, which is why > the system reports an illegal instruction.
Ah, thanks for the clarification. Looks pretty nasty indeed. > Below is a NEXT-by-NEXT trace leading to the failure. I think a real, native backtrace would be more useful, on SPARC for example. > This program is too big for me to create a testcase. I have no idea where > execution is going, only the final failure, which doesn't even allow 'gdb' > to know 'where' we are. Then we are in a dead end because if you, developer/hacker/user of the program, cannot pinpoint the source of the ill-execution, we cannot either. We have neither the time nor the resources to debug every miscompiled program; you have to do half of the work, we'll do the other half. Thanks. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25791
