Mercurial > repos > blastem
comparison debug.c @ 867:bacd67a82d58
Properly initialize commands when adding a new breakpoint
author | Michael Pavone <pavone@retrodev.com> |
---|---|
date | Fri, 06 Nov 2015 13:44:21 -0800 |
parents | 305c85c0b954 |
children | 38dca41f151d |
comparison
equal
deleted
inserted
replaced
866:69a6ec208111 | 867:bacd67a82d58 |
---|---|
400 zinsert_breakpoint(context, value, (uint8_t *)zdebugger); | 400 zinsert_breakpoint(context, value, (uint8_t *)zdebugger); |
401 new_bp = malloc(sizeof(bp_def)); | 401 new_bp = malloc(sizeof(bp_def)); |
402 new_bp->next = zbreakpoints; | 402 new_bp->next = zbreakpoints; |
403 new_bp->address = value; | 403 new_bp->address = value; |
404 new_bp->index = zbp_index++; | 404 new_bp->index = zbp_index++; |
405 new_bp->commands = NULL; | |
405 zbreakpoints = new_bp; | 406 zbreakpoints = new_bp; |
406 printf("Z80 Breakpoint %d set at %X\n", new_bp->index, value); | 407 printf("Z80 Breakpoint %d set at %X\n", new_bp->index, value); |
407 break; | 408 break; |
408 case 'c': | 409 case 'c': |
409 puts("Continuing"); | 410 puts("Continuing"); |