[Top] [All Lists]

Issue with core dump

To: linux-mm <>, Russell King - ARM Linux <>,,,,,,, Andrew Morton <>, Konstantin Khlebnikov <>, KOSAKI Motohiro <>, "Rafael J. Wysocki" <>, Rusty Russell <>, Tejun Heo <>
Subject: Issue with core dump
From: trisha yad <>
Date: Tue, 1 Nov 2011 17:47:24 +0530
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=gLiyolbpNh0eZP671b/USfVcNUTt3pfPRozBCPazPlM=; b=b8cMxrcU+Yua4E4PyAUu0c5hoLDA8vHsQFAuJ/saEjRoEQZstimei94gic4LmVj+Vw jIoFZs/sjas7gEiMEXsuw5vDmvhB9fRzAaOfZlYwnNgdvOpAeKLgfD2QzlJA4XxdkXnL eGSDvGOOH4vWsVzgw+pHk05xOJddHoOF34bxc=
Dear all,

I am running a multithreaded  application. So consider a global
variable x which is used by a, b and c thread.

In thread 'a' do abnormal operation(invalid memory access) and kernel
send signal kill to it. In the mean time Thread 'b' and Thread 'c'
got schedule and update
the variable x. when I got the core file, variable x  got updated, and
I am not  getting actual value that is present at time of crash of
thread a.
But In core file I got updated value of x. I want In core file exact
the same memory status as it at time of abnormal operation(invalid
memory access)

Is there any solution for such problem. ?

I want in core dump the same status  of memory as at time of abnormal
operation(invalid memory access).


<Prev in Thread] Current Thread [Next in Thread>