<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Mark,<br>
    <br>
    good example why not to use addr2line: I think that result is wrong.
    a2l uses gdb which gives:<br>
    <br>
    <tt><a class="moz-txt-link-abbreviated" href="mailto:balzer@leela:~/esp/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3">balzer@leela:~/esp/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3</a>>
      a2l tmp/3.2.007.ovms3.elf 0x400d5e4c:0x3ffc5c40
      0x7ffffffd:0x3ffc5c90<br>
      Using elf file: tmp/3.2.007.ovms3.elf<br>
      0x400d5e4c is in CAN_rxtask(void*)
(/home/openvehicles/build/Open-Vehicle-Monitoring-System-3.1/vehicle/OVMS.V3/components/can/src/can.cpp:730).<br>
      725                  me->IncomingFrame(&msg.body.frame);<br>
      726                } while (loop);<br>
      727              break;<br>
      728              }<br>
      729            case CAN_txcallback:<br>
      730              msg.body.bus->TxCallback(&msg.body.frame,
      true);<br>
      731              break;<br>
      732            case CAN_txfailedcallback:<br>
      733              msg.body.bus->TxCallback(&msg.body.frame,
      false);<br>
      734              msg.body.bus->LogStatus(CAN_LogStatus_Error);<br>
    </tt><tt><br>
    </tt>…and that actually makes sense and matches the register dump.<br>
    <br>
    If I read the gdb disassembly correctly, A10 = msg.body.bus, so
    Greg's got a CAN_txcallback msg without a bus.<br>
    <br>
    Hardening the rxtask against null here would probably avoid the
    crash, but I don't see yet how that could be possible.<br>
    Both esp32can and mcp2515 set the bus field to their object
    addresses, which cannot be null.<br>
    <br>
    Regards,<br>
    Michael<br>
    <br>
    <br>
    <div class="moz-cite-prefix">Am 11.12.19 um 13:45 schrieb Mark
      Webb-Johnson:<br>
    </div>
    <blockquote type="cite"
      cite="mid:1BF79214-A026-4AD0-97D4-5C845FBB0328@webb-johnson.net">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      Can’t get a2l working at the moment. The addr2line gives:
      <div class=""><br class="">
      </div>
      <blockquote style="margin: 0 0 0 40px; border: none; padding:
        0px;" class="">
        <div class="">
          <div class="">addr2line -e 3.2.007.ovms3.elf
            0x400d5e4c:0x3ffc5c40 0x7ffffffd:0x3ffc5c90</div>
          <div class="">/home/openvehicles/build/Open-Vehicle-Monitoring-System-3.1/vehicle/OVMS.V3/components/can/src/can.cpp:551</div>
        </div>
      </blockquote>
      <div class="">
        <div class="">
          <div><br class="">
          </div>
          <div>That is:</div>
          <div><br class="">
          </div>
        </div>
      </div>
      <blockquote style="margin: 0 0 0 40px; border: none; padding:
        0px;" class="">
        <div class="">
          <div class="">
            <div>
              <div>void canbus::LogInfo(CAN_log_type_t type, const char*
                text)</div>
              <div>  {</div>
              <div>  MyCan.LogInfo(this, type, text);    <—— HERE</div>
              <div>  }</div>
            </div>
          </div>
        </div>
      </blockquote>
      <div class="">
        <div class="">
          <div><br class="">
          </div>
          <div>ELF is at:</div>
          <div><br class="">
          </div>
        </div>
      </div>
      <blockquote style="margin: 0 0 0 40px; border: none; padding:
        0px;" class="">
        <div class="">
          <div class="">
            <div><a
href="http://api.openvehicles.com/firmware/ota/v3.2/main/3.2.007.ovms3.elf"
                class="" moz-do-not-send="true">http://api.openvehicles.com/firmware/ota/v3.2/main/3.2.007.ovms3.elf</a></div>
          </div>
        </div>
      </blockquote>
      <div class="">
        <div class="">
          <div><br class="">
          </div>
          <div>Regards, Mark.</div>
          <div><br class="">
            <blockquote type="cite" class="">
              <div class="">On 11 Dec 2019, at 5:20 PM, Michael Balzer
                <<a href="mailto:dexter@expeedo.de" class=""
                  moz-do-not-send="true">dexter@expeedo.de</a>>
                wrote:</div>
              <br class="Apple-interchange-newline">
              <div class="">
                <meta http-equiv="Content-Type" content="text/html;
                  charset=UTF-8" class="">
                <div class="">
                  <div class="moz-cite-prefix">Mark,<br class="">
                    <br class="">
                    Greg uses your build, the crash point seems to be
                    consistent, can you post the a2l on this?<br
                      class="">
                    <br class="">
                    Regards,<br class="">
                    Michael<br class="">
                    <br class="">
                    PS: Greg, would you mind switching to EAP to beta
                    test future releases?<br class="">
                    <br class="">
                    <br class="">
                    Am 11.12.19 um 04:33 schrieb Greg D.:<br class="">
                  </div>
                  <blockquote type="cite"
                    cite="mid:48cd3f20-409f-d201-640a-31b6e7788e92@gmail.com"
                    class="">
                    <pre class="moz-quote-pre" wrap="">Hi folks,

Well, the module updated to 3.2.007 last night.  I just checked on it,
and it appears that it didn't exactly survive.  Crashed while running
the autoconfig script.  Log with two cycles attached.

I tried renaming the /store/events directory to /store/was_events since
it seems like Duktape was getting in the way, but that didn't resolve
the crash.  I manually enabled wifi so I could manage the module, and
moved it back to 3.2.005 from the other partition.  Seems stable again.

The car is going into the Service Center tomorrow (the perennial issue
with 1146 alerts), so I need to have the module stable so that I can
keep an eye on it.  Going to leave it on 3.2.005 for now, unless someone
has a quick fix in the next few hours...

Otherwise, any ideas for troubleshooting after I get the car back back
(hopefully end of day)?

Greg

</pre>
                    <br class="">
                    <fieldset class="mimeAttachmentHeader"></fieldset>
                    <pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
                  </blockquote>
                  <br class="">
                  <br class="">
                  <pre class="moz-signature" cols="144">-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
                </div>
                _______________________________________________<br
                  class="">
                OvmsDev mailing list<br class="">
                <a href="mailto:OvmsDev@lists.openvehicles.com" class=""
                  moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
                  class="">
                <a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
                  class="">
              </div>
            </blockquote>
          </div>
          <br class="">
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="160">-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
  </body>
</html>