Hi,
> 6. regarding re-creating a live process from a core file - some people
> already thought about this (as usual). here is an example (i didn't try
> this yet):
>
> http://www.geocities.com/asimshankar/checkpointing/
A long time ago, there was a [n almost] standard UNIX command cal
Also, if anyone has information on "the quick and easy way" to debug libc
functions (such as tzset), I'd much appreciate it.
On Mon, May 4, 2009 at 11:34 PM, Hai Zaar wrote:
> On Mon, May 4, 2009 at 10:04 PM, guy keren wrote:
> >
> > i think there was something else we wanted an answer for - do
On Mon, May 4, 2009 at 10:04 PM, guy keren wrote:
>
> i think there was something else we wanted an answer for - does anyone
> remember?
Hi, Guy!
Thank for the real goo lecture.
I remind you address these topic mentioned today but not covered:
* Debugging python C modules
* Share you experience ab
1. clarification: the command 'watch *(char*)0x65476 == 0'
puts a hardware watch-point for a single byte at the given address.
if you want to find a change to an item with a different size (e.g. 4
bytes), use a different cast: 'watch *(int*)0x65476 == 0'
2. regarding the 'x' command and end
