Program crash - how to trace the cause


Results 1 to 6 of 6

Threaded View

  1. #4
    Join Date
    May 2013
    Location
    australia
    Posts
    2,653


    Did you find this post helpful? Yes | No

    Default Re: Program crash - how to trace the cause

    the manual says you can nest subs 27 levels deep on a pic18 , but that number includes any use of the stack by interrupts also.
    and that "The only PBP commands that are cause for concern when nesting are GOSUB and CALL. All other PBP commands may be nested with no stack concerns and no practical limit "

    edit
    that's pbp3
    Last edited by richard; - 3rd April 2014 at 12:28. Reason: clarify

Similar Threads

  1. Is there any way to debug/watch/trace macros?
    By mister_e in forum General
    Replies: 1
    Last Post: - 11th July 2011, 23:54
  2. how can i debug & trace my program
    By omid_juve in forum mel PIC BASIC Pro
    Replies: 5
    Last Post: - 17th December 2007, 17:10
  3. HIDmaker from Trace Systems
    By Christopher4187 in forum USB
    Replies: 1
    Last Post: - 23rd March 2006, 22:14
  4. PBP / XP Crash
    By pondindustrial in forum mel PIC BASIC Pro
    Replies: 1
    Last Post: - 27th November 2005, 03:16
  5. maximum oscillator trace length
    By woodygjw in forum Off Topic
    Replies: 8
    Last Post: - 20th May 2005, 03:16

Members who have read this thread : 0

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts