Problem with CVS build

Problem with CVS build

[David Ronis]

Hi,

I follow xconq via cvs.  I updated today and unfortunately the resulting 
binary aborts:  I get

alloc: invalid block: 0x82a8ad8: 0 0 74

Abort

I'm on a linux (slackware) box and am using gcc-3.3.2 to build.

David

P.S., I'm not a subscriber to this list and would appreciate a CC of any 
reply.

Re: Problem with CVS build

[Eric McDonald]

Hi David,

On Tue, 25 Nov 2003, David Ronis wrote:

> I follow xconq via cvs.  I updated today and unfortunately the resulting 
> binary aborts:  I get
> 
> alloc: invalid block: 0x82a8ad8: 0 0 74

Can you tell me which interface you are building. If you just do 
"make" then it should be the Tcl/Tk interface, unless you have 
overriden that with the --enable-ui config option.

Also, do you have any chance of running Xconq in gdb or another 
debugger, so that you can get a backtrace of the call stack?

And does your Xconq.Warnings file show anything of interest?

If you don't have gdb, you cam run Xconq in debug mode with the 
"-D" switch, and, presuming that it doesn't abort immediately you 
might be able to guestimate where the abort is happening.

> I'm on a linux (slackware) box and am using gcc-3.3.2 to build.

Slackware? It's been awhile since I've heard that distro 
mentioned.

  Thanks,
   Eric

Re: Problem with CVS build

[Hans Ronne]

>Hi,
>
>I follow xconq via cvs.  I updated today and unfortunately the resulting
>binary aborts:  I get
>
>alloc: invalid block: 0x82a8ad8: 0 0 74
>
>Abort
>
>I'm on a linux (slackware) box and am using gcc-3.3.2 to build.

Any idea when the problem first appeared? When was the last time you
updated before today?

Hans