Re: cooledit segfault on powerpc (was Re: Help with #123015 on cooledit)

2001-12-29 Thread Aaron Schrab
At 15:40 +0100 29 Dec 2001, Michael Schmitz <[EMAIL PROTECTED]> wrote: > That's what it looked like from the gdb trace. I'll keep your patch > solution around - even where __va_copy is defined for other archs it > should not hurt to use it and work on a copy of va_list, right? Since archs that don

Re: cooledit segfault on powerpc (was Re: Help with #123015 on cooledit)

2001-12-29 Thread Daniel Jacobowitz
On Sat, Dec 29, 2001 at 03:40:31PM +0100, Michael Schmitz wrote: > > > Does anyone have time to dig into bug #123015 a little? I've tried the > > > obvious fix (make sure the built-in CRASHES_ON_STARTUP workaround is > > > defined :)), but Mark Brown says that doesn't help. The only unstable > > >

Re: cooledit segfault on powerpc (was Re: Help with #123015 on cooledit)

2001-12-29 Thread Michael Schmitz
> > Does anyone have time to dig into bug #123015 a little? I've tried the > > obvious fix (make sure the built-in CRASHES_ON_STARTUP workaround is > > defined :)), but Mark Brown says that doesn't help. The only unstable > > Another occurrence of reusing a va_list variable. Although in this > cas

Re: cooledit segfault on powerpc (was Re: Help with #123015 on cooledit)

2001-12-29 Thread Mark Brown
On Sat, Dec 29, 2001 at 04:03:52AM -0600, Aaron Schrab wrote: > Another occurrence of reusing a va_list variable. Although in this > case, it looks like it was just an oversight. In addition to fixing That worked. I'm uploading just now. -- "You grabbed my hand and we fell into it, like a da

Re: Help with #123015 on cooledit

2001-12-29 Thread Michael Schmitz
> Does anyone have time to dig into bug #123015 a little? I've tried the Looking at the bug report: A backtrace of the crash: #0 0x0fb24568 in strlen () from /lib/libc.so.6 #1 0x0faf52ac in vfprintf () from /lib/libc.so.6 #2 0x0fb0f890 in vsprintf () from /lib/libc.so.6 #3 0x0ff9a754 in vspr

cooledit segfault on powerpc (was Re: Help with #123015 on cooledit)

2001-12-29 Thread Aaron Schrab
At 18:16 -0600 28 Dec 2001, Colin Watson <[EMAIL PROTECTED]> wrote: > Does anyone have time to dig into bug #123015 a little? I've tried the > obvious fix (make sure the built-in CRASHES_ON_STARTUP workaround is > defined :)), but Mark Brown says that doesn't help. The only unstable Another occurr

Re: Bug#123015: Help with #123015 on cooledit

2001-12-29 Thread Taral
On Fri, Dec 28, 2001 at 11:43:42PM -0600, Taral wrote: > I'll see if I can get a hold of my friend's debian/ppc box and look into > this. (gdb) run Starting program: /usr/bin/X11/cooledit [New Thread 1024 (LWP 19837)] cooledit:stringtools.c:537: vsprintf wrote out of bounds Program received sign

Re: Bug#123015: Help with #123015 on cooledit

2001-12-28 Thread Taral
On Fri, Dec 28, 2001 at 06:16:51PM -0600, Colin Watson wrote: > Does anyone have time to dig into bug #123015 a little? I've tried the > obvious fix (make sure the built-in CRASHES_ON_STARTUP workaround is > defined :)), but Mark Brown says that doesn't help. The only unstable > powerpc machine I c

Help with #123015 on cooledit

2001-12-28 Thread Colin Watson
Does anyone have time to dig into bug #123015 a little? I've tried the obvious fix (make sure the built-in CRASHES_ON_STARTUP workaround is defined :)), but Mark Brown says that doesn't help. The only unstable powerpc machine I can access is voltaire, and since that doesn't seem to accept ssh X for