On Tue, 21 Jun 2005, KV Pavuram wrote:
I am running a multithreaded application on Linux 2.4
kernel (RedHat Linux 9).
At some point the program receives a seg. fault and if
i check info threads, using gdb for debug, almost all
the threads are at "0xffffe002 in ??"
If a number of threads arrive at the same bad address you
should look for some common code that calls through
a function pointer. If you don't have any calls through
pointers, then you may have something corrupting the stack
so that the return address of a called function gets
corrupted. For instance, if the value 0x02e0 was written
beyond array limits in local (stack) data, then when that
function returned it could actually end up 'returning'
to the bad address you discovered.
Although the kernel provided the seg-fault mechanism, this
is not a kernel problem. This is a user-code problem.
When I switch to each of these tasks, and try x/i for
0xffffe002, cannot access address.
What could be the problem?
Please help.
Regards,
Pav.
Cheers,
Dick Johnson
Penguin : Linux version 2.6.12 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached for review by Dictator Bush.
98.36% of all statistics are fiction.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
