Hello, I've got a quick couple of questions. I'm debugging a program, and don't have sym tables loaded. I'd like to figure out how to get the most information possible. I'd like to obtain function lists, if possible, and memory values, which I think is all I can really get. My question is this, I know I can set breakpoints, and do a backtrace that way, but how would memory values be readable? I can start at the beginning of the program's memory and traverse through the memory, but it ends up showing up as a bunch of chars, is there a way I can translate this? Any tips would be welcome--I think I need more debugging knowledge than I currently have. I'm interested in working with windbg and dbg for linux, so I can learn the techniques of both. also, an off question, When a dll is mapped into memory for a program on windows, Is the dll's memory shared, or does each program map it's own individual dll? I think that's about it. I'm basically trying to dig into the internals of how things work, how memory is managed, etc and trying to learn how to debug things along the way. A book or two on windows's inner-workings would be awesome, I understand how the message queue and etc works, but I think I have a ways to go in memory management and etc. Also, I've learned how to use kernel modules in linux, if a need ever arises. I'd love to be able to learn how the ddk works and driver development for windows, if anyone can point me toward a book or resource there too.
Thanks, ~~TheCreator~~ Visit TDS for quality software and website production http://tysdomain.com visit the piratecafe for programming related resources: http://piratecafe.net msn: [EMAIL PROTECTED] skype: st8amnd127 [Non-text portions of this message have been removed]
