Re: [evolution-patches] Patch for CamelURL



Odd. Maybe something inadvertently fixed the problem that was exposing
the bug in CamelURL. I was getting it when I switched to IMAP4, but now
that I've removed the patch to try to make it crash again, it doesn't
crash any more. Hrmmmmmm...

-- dobey

On Tue, 2005-01-25 at 08:14 +0800, Not Zed wrote:
> 
> Oh, well it should really have a bug report, if its against stable at
> least.
> 
> Can you create one and attach a backtrace?  If its dereferencing path
> when it shouldn't be, it probably just needs to not dereference it,
> but i'd like to see the specific case, since i've not ever seen this.
> 
> On Mon, 2005-01-24 at 11:57 -0500, Rodney Dawes wrote: 
> > I don't know if there is a specific bug # for this... I haven't filed
> > one. I can get a backtrace and file one though. Basically, base->path
> > is being set to NULL somewhere, and it's crashing in the strrchr ()
> > call right after where I added this strdup.
> > 
> > -- dobey
> > 
> > On Mon, 2005-01-24 at 13:28 +0800, Not Zed wrote:
> > > 
> > > This is wrong, for starters, base is a read-only input to the
> > > function.
> > > 
> > > What bug number/report is this supposed to be fixing?
> > > 
> > > 
> > > On Sun, 2005-01-23 at 23:11 -0500, Rodney Dawes wrote: 
> > > > Here's a patch to make sure base->path is never NULL. Currently it can
> > > > be NULL sometimes, and causes a crash when it hits the strrchr() call
> > > > in the same function.
> > > > 
> > > > -- dobey
> > > > 
> > 




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]