In reference to my original message at:
http://sources.redhat.com/ml/bug-gdb/2000-12/msg00064.html
It seemed like this proposed patch by John Love-Jensen could
solve my problem:
http://sources.redhat.com/ml/bug-gdb/2000-12/msg00073.html
But it did not.
The original bug report by John was here:
http://sources.redhat.com/ml/bug-gdb/2000-12/msg00059.html
I replaced the _last_ 'return (pst);' statement in the
function find_pc_sect_psymtab() [symtab.c] with the 'best = pst;'
statement. I also replaced the final 'return NULL;' statement
with 'return (best);'. The variable 'best' is initialized to NULL
at the beginning of the function.
The end of the function now looks like this:
/*return (pst);*/
/* Best we've got so far, but it's still unimpressive. */
/* Maybe a more likely match further down the chain. */
best = pst;
}
}
return (best); /* @sarrazip 20001220 */
}
However, my own problem persists.
Is there a small piece of code that produces the original bug?
I could run it on my machine to try to study the problem a bit more.
--
Pierre Sarrazin <sarrazip at machinasapiens dot com>
_______________________________________________
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
