All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
	alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH] amixer: add support for TLV byte control read
Date: Thu, 28 Jan 2016 14:56:44 +0530	[thread overview]
Message-ID: <20160128092644.GJ11130@localhost> (raw)
In-Reply-To: <s5hzivqmewz.wl-tiwai@suse.de>

On Thu, Jan 28, 2016 at 06:49:48AM +0100, Takashi Iwai wrote:
> > Yes did, but didn't get a clue. tlv seems to be valid before free and points
> > to right location and contents
> 
> Could you show the backtrace?

676                     if ((err = snd_hctl_elem_tlv_read(elem, tlv, 4096)) < 0) {
(gdb) n
677                             error("Control %s element TLV read error: %s\n", card, snd_strerror(err));
(gdb) p err
$1 = -14

(gdb) n
amixer: Control hw:0 element TLV read error: Bad address

678                             free(tlv);
(gdb) p tlv
$2 = (unsigned int *) 0x625f10
(gdb) p tlv[0]
$3 = 4294967295
(gdb) p tlv[1]
$4 = 0
(gdb) backtrace
#0  show_control (elem=0x625310, level=level@entry=5, space=0x409b01 "  ")
at amixer.c:678
#1  0x00000000004066d9 in cset (argc=argc@entry=1, argv=0x7fffffffe530,
roflag=roflag@entry=1, keep_handle=keep_handle@entry=0) at amixer.c:1184
#2  0x0000000000404352 in main (argc=<optimized out>, argv=0x7fffffffe518)
at amixer.c:1863
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff749e12f in _int_free (av=0x7ffff77dd760 <main_arena>,
p=<optimized out>, have_lock=0) at malloc.c:3996
3996    malloc.c: No such file or directory.
(gdb) backtrace
#0  0x00007ffff749e12f in _int_free (av=0x7ffff77dd760 <main_arena>,
p=<optimized out>, have_lock=0) at malloc.c:3996
#1  0x00000000004063be in show_control (elem=0x625310, level=level@entry=5,
space=0x409b01 "  ") at amixer.c:678
#2  0x00000000004066d9 in cset (argc=argc@entry=1, argv=0x7fffffffe530,
roflag=roflag@entry=1, keep_handle=keep_handle@entry=0) at amixer.c:1184
#3  0x0000000000404352 in main (argc=<optimized out>, argv=0x7fffffffe518)
at amixer.c:1863

-- 
~Vinod

  reply	other threads:[~2016-01-28  9:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22  5:46 [PATCH] amixer: add support for TLV byte control read Vinod Koul
2016-01-22  6:19 ` Takashi Iwai
2016-01-22  7:46   ` Vinod Koul
2016-01-22  8:09     ` Takashi Iwai
2016-01-22  8:26       ` Takashi Iwai
2016-01-22  9:57         ` Vinod Koul
2016-01-22  9:56       ` Vinod Koul
2016-01-22 10:50         ` Takashi Iwai
2016-01-27 17:47           ` Vinod Koul
2016-01-27 18:49             ` Takashi Iwai
2016-01-28  4:25               ` Vinod Koul
2016-01-28  5:49                 ` Takashi Iwai
2016-01-28  9:26                   ` Vinod Koul [this message]
2016-01-28 16:19                     ` Takashi Iwai
2016-01-29  6:51                       ` Vinod Koul
2016-01-29 11:13                         ` Vinod Koul
2016-01-29 13:17                           ` Takashi Iwai
2016-01-29 13:53                             ` Vinod Koul
2016-01-29 13:53                               ` Takashi Iwai

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=20160128092644.GJ11130@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.com \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.