public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jengelh at inai dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14376] glibc-2.16 strdup Illegal Instruction on sparc64
Date: Mon, 17 Sep 2012 08:15:00 -0000	[thread overview]
Message-ID: <bug-14376-131-TultsZgLHO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14376-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14376

Jan Engelhardt <jengelh at inai dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |ASSIGNED

--- Comment #4 from Jan Engelhardt <jengelh at inai dot de> 2012-09-17 08:15:17 UTC ---
__strdup (s=0x1008e0 "") at strdup.c:40
40      {
(gdb) 
41        size_t len = strlen (s) + 1;
(gdb) n
42        void *new = malloc (len);
(gdb) p len
$3 = 1
(gdb) n
44        if (new == NULL)
(gdb) 
47        return (char *) memcpy (new, s, len);
(gdb) si
0xfffff80100099f08      47        return (char *) memcpy (new, s, len);
(gdb) 
0xfffff8010026f4a0 in _Qp_xtoq@plt () from ./libc.so.6
(gdb) disas
Dump of assembler code for function _Qp_xtoq@plt:
   0xfffff8010026f460 <+0>:     b,a   0xfffff8010013a840 <_Qp_xtoq>
   0xfffff8010026f464 <+4>:     b,a   %xcc, 0xfffff8010026f320
   0xfffff8010026f468 <+8>:     nop 
   0xfffff8010026f46c <+12>:    nop 
   0xfffff8010026f470 <+16>:    nop 
   0xfffff8010026f474 <+20>:    nop 
   0xfffff8010026f478 <+24>:    nop 
   0xfffff8010026f47c <+28>:    nop 
   0xfffff8010026f480 <+32>:    illtrap  0
   0xfffff8010026f484 <+36>:    illtrap  0x45804
   0xfffff8010026f488 <+40>:    nop 
   0xfffff8010026f48c <+44>:    nop 
   0xfffff8010026f490 <+48>:    nop 
   0xfffff8010026f494 <+52>:    nop 
   0xfffff8010026f498 <+56>:    nop 
   0xfffff8010026f49c <+60>:    nop 
=> 0xfffff8010026f4a0 <+64>:    illtrap  0
   0xfffff8010026f4a4 <+68>:    illtrap  0xa0b20
   0xfffff8010026f4a8 <+72>:    nop 
   0xfffff8010026f4ac <+76>:    nop 
   0xfffff8010026f4b0 <+80>:    nop 
   0xfffff8010026f4b4 <+84>:    nop 
   0xfffff8010026f4b8 <+88>:    nop 
---Type <return> to continue, or q <return> to quit---q
Quit
(gdb) si

Program received signal SIGILL, Illegal instruction.
0xfffff8010026f4a0 in _Qp_xtoq@plt () from ./libc.so.6
(gdb)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-09-17  8:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 10:25 [Bug libc/14376] New: " jengelh at medozas dot de
2012-07-20 10:26 ` [Bug libc/14376] " jengelh at medozas dot de
2012-07-20 10:35 ` aj at suse dot de
2012-07-20 10:43 ` aj at suse dot de
2012-07-24  1:38 ` davem at davemloft dot net
2012-07-24  1:43 ` carlos_odonell at mentor dot com
2012-09-17  8:15 ` jengelh at inai dot de [this message]
2012-09-17  8:24 ` jengelh at inai dot de
2012-09-17  9:58 ` jengelh at inai dot de
2012-09-17 16:18 ` davem at davemloft dot net
2012-09-17 16:29 ` davem at davemloft dot net
2012-09-17 21:15 ` jengelh at inai dot de
2012-09-28  4:25 ` davem at davemloft dot net
2012-09-28  7:01 ` jengelh at inai dot de
2012-09-28  7:20 ` davem at davemloft dot net
2014-06-17 18:57 ` fweimer at redhat 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-14376-131-TultsZgLHO@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).