Strange error " Unexpected BOARD::MarkTrace: multiple pad_on_start"

[Simon Hilton]

Took a while to figure out what was causing it, but I started getting the error

"Unexpected BOARD::MarkTrace: multiple pad_on_start"

When selecting a trace in my design...

I narrowed down what was causing it, I had a via at the snap point of a pad of a pull up resistor i was using. moving the via off the snap point stopped the error.

The bug is that there was an error message at all.

Was asked to report it, So reporting it.

Version info
Application: kicad
Version: (5.1.2)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

[MightyPork (mighty-pork)]

I had this happen on a bigger board and never figured out what was causing it. Exported gerbers, made the board, all good.

[Wayne Stambaugh (stambaughw)]

I cannot duplicate this using the conditions you described. Would it be possible to attach the board file that caused the issue to this bug report? I would also need to know which trace to select to trigger the bug.

[Simon Hilton (mangy-dog)]

Im afraid I cant, but ive also already done the work around by taking the via off the pad snap point.

Sent from Mail for Windows 10

From: Wayne Stambaugh
Sent: 05 August 2019 13:41
To: <email address hidden>
Subject: [Bug 1838261] Re: Strange error " Unexpected BOARD::MarkTrace:multiple pad_on_start"

I cannot duplicate this using the conditions you described. Would it be
possible to attach the board file that caused the issue to this bug
report? I would also need to know which trace to select to trigger the
bug.

** Changed in: kicad
       Status: New => Incomplete

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1838261

Title:
  Strange error " Unexpected BOARD::MarkTrace: multiple pad_on_start"

Status in KiCad:
  Incomplete

Bug description:
  Took a while to figure out what was causing it, but I started getting
  the error

  "Unexpected BOARD::MarkTrace: multiple pad_on_start"

  When selecting a trace in my design...

  I narrowed down what was causing it, I had a via at the snap point of
  a pad of a pull up resistor i was using. moving the via off the snap
  point stopped the error.

  The bug is that there was an error message at all.

  Was asked to report it, So reporting it.

  Version info
  Application: kicad
  Version: (5.1.2)-1, release build
  Libraries:
      wxWidgets 3.0.4
      libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.68.0
      OpenCASCADE Community Edition: 6.9.1
      Curl: 7.61.1
      Compiler: GCC 8.2.0 with C++ ABI 1013

  Build settings:
      USE_WX_GRAPHICS_CONTEXT=OFF
      USE_WX_OVERLAY=OFF
      KICAD_SCRIPTING=ON
      KICAD_SCRIPTING_MODULES=ON
      KICAD_SCRIPTING_PYTHON3=OFF
      KICAD_SCRIPTING_WXPYTHON=ON
      KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
      KICAD_SCRIPTING_ACTION_MENU=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_USE_OCC=OFF
      KICAD_SPICE=ON

To manage notifications about this bug go to:
https://bugs.launchpad.net/kicad/+bug/1838261/+subscriptions

[Wayne Stambaugh (stambaughw)]

@Simon, I placed a via on a pad snap point and could not trigger the assert so there must be something more to it than that. If you manage to trigger it again, please attach the board to this bug report so I can attempt to duplicate it.

[Simon Hilton (mangy-dog)]

Ok will do sorry I couldn’t be more help

Sent from Mail for Windows 10

From: Wayne Stambaugh
Sent: 07 August 2019 20:30
To: <email address hidden>
Subject: [Bug 1838261] Re: Strange error " Unexpected BOARD::MarkTrace:multiple pad_on_start"

@Simon, I placed a via on a pad snap point and could not trigger the
assert so there must be something more to it than that. If you manage
to trigger it again, please attach the board to this bug report so I can
attempt to duplicate it.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1838261

Title:
  Strange error " Unexpected BOARD::MarkTrace: multiple pad_on_start"

Status in KiCad:
  Incomplete

Bug description:
  Took a while to figure out what was causing it, but I started getting
  the error

  "Unexpected BOARD::MarkTrace: multiple pad_on_start"

  When selecting a trace in my design...

  I narrowed down what was causing it, I had a via at the snap point of
  a pad of a pull up resistor i was using. moving the via off the snap
  point stopped the error.

  The bug is that there was an error message at all.

  Was asked to report it, So reporting it.

  Version info
  Application: kicad
  Version: (5.1.2)-1, release build
  Libraries:
      wxWidgets 3.0.4
      libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.68.0
      OpenCASCADE Community Edition: 6.9.1
      Curl: 7.61.1
      Compiler: GCC 8.2.0 with C++ ABI 1013

  Build settings:
      USE_WX_GRAPHICS_CONTEXT=OFF
      USE_WX_OVERLAY=OFF
      KICAD_SCRIPTING=ON
      KICAD_SCRIPTING_MODULES=ON
      KICAD_SCRIPTING_PYTHON3=OFF
      KICAD_SCRIPTING_WXPYTHON=ON
      KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
      KICAD_SCRIPTING_ACTION_MENU=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_USE_OCC=OFF
      KICAD_SPICE=ON

To manage notifications about this bug go to:
https://bugs.launchpad.net/kicad/+bug/1838261/+subscriptions

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[Otto Mikkonen (ottomaani138)]

Hey!
I also came across an identical error scenario as the op!
Selecting a trace all of a sudden triggered a never-seen-before warning stating:
"Unexpected BOARD::MarkTrace: multiple pad_on_start"
I found this thread while looking for similar experiences, and motivated by this thread I tried removing a via that I had placed on top of a measuring point.
Removing the via got rid of the error message for me.
See the attached screenshots to see the scenario where the error was produced.

Interestingly enough, when I now try to replicate the issue by adding a new via to where it used be before removing it, I can't replicate the error message.
Also, I also had other places on my board design where an identical measuring point was pierced by an identical via, and I wasn't able to reproduce the error there either.

If I re-counter the issue again in a way that I can continuously reproduce it I'll try to provide the board-file to help solve the case!

[Otto Mikkonen (ottomaani138)]

Here's another screenshot of the scenario when the via was removed and no error was produced when selecting the trace.

Also, version information

##

Application: Pcbnew
Version: 5.1.4-e60b266~84~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-64-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.22
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.4.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

[Seth Hillbrand (sethh)]

I haven't been able to see this yet but multiple people are reporting it, so we need to address it.

[Enrico (eatis)]

Experienced the same today. I can't tell you how to reproduce it but the comments helped me to narrow it down if I stumble upon the bug another time. One interesting thing it that if I use the "U" hotkey (select single track) the attached warning is shown, but when I pressed "I" (select connected tracks) on the same segment the warning looked like in #6, without the "Details". I will keep my eyes open and see if I can provoke it again.

Application: KiCad
Version: 5.1.4-e60b266~84~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-70-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.22
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.4.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

[Ian McInerney (imcinerney)]

Does anyone seeing this warning have any Python action plugins installed? I was trying to see where this could be coming from, and the only place that I see any reference to BOARD::MarkTrace is in the Python bindings.

[Seth Hillbrand (sethh)]

@Ian, this will be only in the 5.1 branch

[Enrico (eatis)]

The error occurred again in my project and I managed to isolate it. See attached board file. To provoke it use either "Select Single Track", "Select Connected Tracks" or "Drag Track Keep Slope" on the "CFG_INIT"-trace on the bottom layer (isn't invoked on the top layer part of the trace).

Hope that helps.

[Michael Kavanagh (michaelkavanagh)]

Reproduces for me.

Application: Pcbnew
Version: (5.1.5-0-10_14), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.1 SecureTransport (LibreSSL/2.8.3) zlib/1.2.11 nghttp2/1.39.2
Platform: Mac OS X (Darwin 19.0.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (wchar_t,STL containers,compatible with 2.8)
    Boost: 1.69.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.54.0
    Compiler: Clang 9.0.0 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

[KiCad Janitor (kicad-janitor)]

KiCad bug tracker has moved to Gitlab. This report is now available here: https://gitlab.com/kicad/code/kicad/-/issues/2554