From: Zhongye Jia <jia.zhongye@gmail.com>
To: Fawad Lateef <fawadlateef@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Hi, Needs suggestions for finding and fixing stack/memory corruption when calling a function
Date: Mon, 23 May 2011 22:59:09 +0800 [thread overview]
Message-ID: <BANLkTikQ0PCeB6rd0Omhzq=J9RFJ2QZyvQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimdU05oVtTdOr7TXdrUvc2NJ7KVyQ@mail.gmail.com>
would you please provide your problem code? according to your
description, it highly seems that some of your pointers accidentally
write that memory, but i'm not sure.
you may use a debugger to watch that block of memory and see when it changed.
On Mon, May 23, 2011 at 10:41 PM, Fawad Lateef <fawadlateef@gmail.com> wrote:
> Hello,
>
> I need some suggestions about how-to approach, find and fix a memory
> corruption issue which is happening in a C/C++ very complex and large
> code (code evolved over several years). Code is running on AT91SAM9260
> (armv5l architecture; single processor with preemption enabled) and
> completely in Linux user-space.
>
> The problem is:
>
> -- We are calling a function which has three integer arguments.
> With-in that function 2nd and 3rd arguments always gets corrupted
> while 1st argument is fine. Just before calling that function printing
> arguments is fine.
>
> Now it will be good if I can get some suggestions about whats
> happening and how-to look into this problem. I am thinking that there
> is some memory/stack corruption happening somewhere.
>
> Thanks in advance.
>
> -- Fawad Lateef
> --
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-23 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTingN-61wOzWKk7iwxFgo0W2YAzUQQ@mail.gmail.com>
2011-05-23 14:41 ` Hi, Needs suggestions for finding and fixing stack/memory corruption when calling a function Fawad Lateef
2011-05-23 14:45 ` Andrej Gelenberg
2011-05-23 14:59 ` Fawad Lateef
2011-05-24 8:29 ` Mahavir Jain
2011-05-23 14:59 ` Zhongye Jia [this message]
[not found] ` <BANLkTimx+=DxYCCqtSKjGWUm63jBAe+iug@mail.gmail.com>
2011-05-24 9:02 ` Fawad Lateef
2011-05-24 12:48 ` Glynn Clements
2011-05-24 15:33 ` Fawad Lateef
2011-05-25 11:07 ` Glynn Clements
2011-06-14 15:25 ` Fawad Lateef
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTikQ0PCeB6rd0Omhzq=J9RFJ2QZyvQ@mail.gmail.com' \
--to=jia.zhongye@gmail.com \
--cc=fawadlateef@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).