public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "prafulla.fin at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17176] backtrace() not working on ARMv7a
Date: Fri, 25 Jul 2014 12:10:00 -0000	[thread overview]
Message-ID: <bug-17176-131-QmV2OztuWZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17176-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17176

--- Comment #3 from prafulla chandra kota <prafulla.fin at gmail dot com> ---
Hi All,

Appreciate if somebody could provide the fix for backtrace for below issue as
an example

void func1() {
  int    val;
  char buf[256];
  val = 100;
  printf("\nTrying to construct invalid buffer!\n");
  snprintf(buf, sizeof (buf), "%s", val);
  printf("The content of buf: %s\n", buf);

}

For other issues like NULL pointer access or invalid memory access, backtrace
is working fine in glibc but not for above type of issues.

For above issue uclibc forum has given fix in below link
http://lists.uclibc.org/pipermail/uclibc/2013-September/047932.html

I am looking for similar fix info or patch, so that i can make changes if
someone points out relevant changes.

Thanks,
Prafulla Kota.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-07-25 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 11:58 [Bug libc/17176] New: " prafulla.fin at gmail dot com
2014-07-18 15:51 ` [Bug libc/17176] " joseph at codesourcery dot com
2014-07-22 10:21 ` prafulla.fin at gmail dot com
2014-07-25 12:10 ` prafulla.fin at gmail dot com [this message]
2014-07-25 15:21 ` joseph at codesourcery dot com

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=bug-17176-131-QmV2OztuWZ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).