[Ltrace-devel] Segfault after a call to exec in ltrace 0.5.3

[Qais Yousef]

Thanks. Yes 0.5.3 is ancient but I'm afraid that's what we have now.
Hopefully we'll move to 0.6.0 soon. Once I have the time I'll try to
test it against the master and report any problems if found.

Cheers,
Qais

> -----Original Message-----
> From: Petr Machata [mailto:pmachata at redhat.com]
> Sent: 20 February 2012 13:45
> To: Qais Yousef
> Cc: ltrace-devel at lists.alioth.debian.org
> Subject: Re: [Ltrace-devel] Segfault after a call to exec in ltrace
0.5.3
> 
> Qais Yousef <Qais.Yousef at imgtec.com> writes:
> 
> > I've been encountering a segfault that according to the printed
debug
> > messages always happens after a call to exec(). I am not familiar
with
> > the code but my attempt to understand the cause lead me to create
the
> > attached patch which seems to fix the problem for me.
> 
> Thanks for the report.  Ltrace 0.5.3 is pretty ancient.  The latest
released
> version is 0.6.0, and that is relatively old already and many fixes
and changes
> went in since.  Would you be so kind as to test whether your scenario
breaks
> current master branch?
> 
> Thank you,
> PM