ביום ראשון 07 דצמבר 2003, 18:43, נכתב על ידי Muli Ben-Yehuda: > On Sun, Dec 07, 2003 at 06:24:02PM +0200, Oded Arbel wrote: > > But they don't. instead they have memory addresses and the function name. > > so I've been thinking - suppose I have a binary with debugging > > information, and the source code and a stack trace - shouldn't I be able > > to extrapolate from it in what line in the code each frame in the stack > > is ? > > Of course. disassemble each function, and correlate memory address in > the disassembly to the memory address you have. Am I missing > something?
Nothing that I can think of. I had the the idea that it should work out something like how you describe, but I guess I was hoping to get a more pragmatic answer, maybe pointing me at some utilities that already do part of the work - I don't fancy doing this myself, as I haven't got the time. Then I got objdump to give me all the info that I need, so I'm ok now, thanks :-) -- Oded ::.. Real punks help little old ladies across the street because it shocks more people than if they spit on the sidewalk. ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
