KiCad

Core dump on creating part Build 2014-05-05 BZR 4851

Asked by Scott Stansberry

Using PCBNew and trying to create a footprint. When I try to add an outline to the footprint, Kicad coredumps with the following message:

*** Error in `kicad': free(): invalid pointer: 0x00007f47497157b8 ***

I'm using Ubuntu 14.04 x64. The problem is repeatable and rebooting machine and reinstalling kicad doesn't help. It also immediately coredumps when trying to create a footprint in a project without a schematic. I found this out by accident after a reboot, but thought I'd add the detail if it helps debug. Is this a bug or am I doing something wrong? I've created footprints before, but it's been a few weeks.

Question information

Language:
English Edit question
Status:
Solved
For:
KiCad Edit question
Assignee:
No assignee Edit question
Solved by:
Dick Hollenbeck
Solved:
Last query:
Last reply:
Revision history for this message
Dick Hollenbeck (dickelbeck) said : 		#1

On 05/05/2014 03:51 PM, Scott Stansberry wrote:
> New question #248213 on KiCad:
> https://answers.launchpad.net/kicad/+question/248213
>
> Using PCBNew and trying to create a footprint. When I try to add an outline to the footprint, Kicad coredumps with the following message:
>
> *** Error in `kicad': free(): invalid pointer: 0x00007f47497157b8 ***
>
> I'm using Ubuntu 14.04 x64. The problem is repeatable and rebooting machine and reinstalling kicad doesn't help. It also immediately coredumps when trying to create a footprint in a project without a schematic. I found this out by accident after a reboot, but thought I'd add the detail if it helps debug. Is this a bug or am I doing something wrong? I've created footprints before, but it's been a few weeks.
>
>

Hi Scott,

1) What are the keystrokes or mouse clicks required to reproduce this please?

2) Are you building this yourself and if so how, or are you downloading it from somewhere?

3) Do you want to be on the bleeding edge, or would you prefer to back off, avoiding the
currently rapidly changing code? Being there is not as risky if you can rebuild fast,
and you can report bugs well enough for them to get duplicated and fixed. So all these
questions help establish the situation and sort of go together.

Revision history for this message
Scott Stansberry (stansb) said : 		#2

1) open PCBNew. click Open Module Editor, click New Module, enter "foo" when prompted for Enter footprint name, core dump occurs. This is the simplest way to reproduce the coredump, it also happens when editing an existing footprint. I first noticed it then when attempting to modify the part outline.

2) It's an existing legacy part library, although as mentioned in 1 above it also occurs when trying to create a new part. I foolishly(?) ran the kicad-install script today in the middle of a project. That script is dated April 28. I didn't think to check if that has been updated, so will go check now after answering this.

3) I may need to back away from the edge. :-) I see there is a bug report and I added myself there. Hope the additional detail helps. I would attach the coredump, but I couldn't find it. It isn't in /var/crash or the project directory. Thanks for looking into this.

Revision history for this message
Scott Stansberry (stansb) said : 		#3

Added bug link Bug #1316306

Revision history for this message
Best Dick Hollenbeck (dickelbeck) said : 		#4

On 05/05/2014 04:36 PM, Scott Stansberry wrote:
> Question #248213 on KiCad changed:
> https://answers.launchpad.net/kicad/+question/248213
>
> Scott Stansberry posted a new comment:
> 1) open PCBNew. click Open Module Editor, click New Module, enter "foo"
> when prompted for Enter footprint name, core dump occurs. This is the
> simplest way to reproduce the coredump, it also happens when editing an
> existing footprint. I first noticed it then when attempting to modify
> the part outline.
>
> 2) It's an existing legacy part library, although as mentioned in 1
> above it also occurs when trying to create a new part. I foolishly(?)
> ran the kicad-install script today in the middle of a project. That
> script is dated April 28. I didn't think to check if that has been
> updated, so will go check now after answering this.

I fixed the bug.

> 3) I may need to back away from the edge. :-) I see there is a bug
> report and I added myself there. Hope the additional detail helps. I
> would attach the coredump, but I couldn't find it. It isn't in
> /var/crash or the project directory. Thanks for looking into this.

I modified kicad-install.sh to build the

-r tag:pre-kiway

version unless you edit it to TESTING.

I appreciate the testing. In a week I will be using the software much more than I am now
and that will give me a chance and motive flush out even more bugs resulting from new
architecture.

But if you want something that works pretty well, the pre-kiway may be a better choice
rather than the tip of product for another couple of weeks.

Dick

Revision history for this message
Scott Stansberry (stansb) said : 		#5

Thanks Dick Hollenbeck, that solved my question.