All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexis Berlemont <alexis.berlemont@domain.hid>
To: Daniele Nicolodi <daniele@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Analogy a4l_fill_desc() bug
Date: Mon, 28 Jun 2010 00:38:04 +0200	[thread overview]
Message-ID: <20100627223804.GA25991@domain.hid> (raw)
In-Reply-To: <AANLkTimw3WcsILV9AZaHtfB7omLQI4es9i0j53S17vkP@mail.gmail.com>

Hi,

Alexis Berlemont wrote:
> Hi,
> 
> On Wed, Jun 16, 2010 at 7:01 PM, Daniele Nicolodi <daniele@domain.hid> wrote:
> > On 11/03/10 18:12, Daniele Nicolodi wrote:
> >> Hello.
> >>
> >> I found a bug in a4l_fill_desc(). If I call it on a descriptor obtained
> >> for an unattached device, the memory allocated for the sbdata descriptor
> >> field is corrupted in a bad way. When, after the failing a4l_fill_desc()
> >> call, I free() it, glibc complains about an "invalid next size" for the
> >> memory chunk.
> >>
> >> I'm on x86 architecture using kernel 2.6.30.10 with xenomai 2.5.1.
> >
> > This bug is still biting me...
> 
> A few months ago, I fixed a bug in a4l_fill_desc() and I forgot there
> were two. So I closed the case in my TODO list.
> 
> Many thanks for reminding me.
> 

The bug should be fixed in my git repository now (branch analogy).

> >
> > Cheers,
> > --
> > Daniele
> >
> > _______________________________________________
> > Xenomai-core mailing list
> > Xenomai-core@domain.hid
> > https://mail.gna.org/listinfo/xenomai-core
> >
> 
> Alexis.

-- 
Alexis.


      reply	other threads:[~2010-06-27 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 17:12 [Xenomai-core] Analogy a4l_fill_desc() bug Daniele Nicolodi
2010-03-11 17:43 ` Simon Boulay
2010-06-16 17:01 ` Daniele Nicolodi
2010-06-17  6:13   ` Alexis Berlemont
2010-06-27 22:38     ` Alexis Berlemont [this message]

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=20100627223804.GA25991@domain.hid \
    --to=alexis.berlemont@domain.hid \
    --cc=daniele@domain.hid \
    --cc=xenomai@xenomai.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 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.