What debugging tools you use?

walkero · 27 June 2020, 13:13

Hello guys. I would like to ask if you have a list of applications that you use to trace memory leaks and debug issues, on your C programs for 68K CPUs. I am trying to find what is currently the best to use and I found a few of them in aminet, but your feedback is also necessary.

I am developing an app and I have some memory leak which I need to trace and fix it. Any tips and tricks for this as well?

Thank you for your help.

daxb · 27 June 2020, 13:53

MuForce/MuGuardianAngel, Mungwall/MungList, MemSniff, PoolWatch, SegTracker, sashimi. Some are doing the same or are replacements of others but at least that is a start.

Thomas Richter · 27 June 2020, 16:31

MuForce, MuGA, Wipeout, segtracker, COP and a PC with a null-modem cable. Mungwall I can no longer recommend, replace it by Wipeout. The problem with MungWall is that it contains a crude workaround for a "feature" of the v37 layers.library that is quite disruptive with newer versions of the Os and caused some "false positives" when debugging 3.1.4.

I believe the most important debugging tool for 3.1.4 was COP.

walkero · 27 June 2020, 16:59

Thank you guys for your reccommendations. Do you have any tips on any of these apps, or do you know a good guide on how to use any of them? This could be a good guide for any new developer like me

PeterK · 27 June 2020, 17:45

In addition to all those tools that were already mentioned here I'm also using LibSnooper which can report about any library function call, the register contents, the result and the task, but of course, can also be used to monitor AllocVec(), AllocMem(), AllocBitMap(), FreeVec(), FreeMem(), FreeBitMap() for example or whatever you want to know.

Thomas Richter · 27 June 2020, 17:51

In terms of system tools, there is of course SnoopDos (shows most important system tools), Xoper (shows most important system lists) and SaferPatches/ShowPatches (shows system patches).

Concerning documentation: MuForce and COP come with an extensive guide/manual. For COP, there is also a tutorial in German: https://www.a1k.org/forum/index.php?threads/73115/

Hedeon · 27 June 2020, 18:55

COP and Snoopy. is LibSnooper better?

27 June 2020, 13:13	#1
walkero Registered User Join Date: May 2012 Location: Dublin/Ireland Posts: 358	What debugging tools you use? Hello guys. I would like to ask if you have a list of applications that you use to trace memory leaks and debug issues, on your C programs for 68K CPUs. I am trying to find what is currently the best to use and I found a few of them in aminet, but your feedback is also necessary. I am developing an app and I have some memory leak which I need to trace and fix it. Any tips and tricks for this as well? Thank you for your help.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Debugging	guy lateur	support.Amiga Forever	10	21 October 2018 16:20
Debugging help	mop	Coders. C/C++	5	20 April 2018 08:37
3.6.0 Debugging Mode	bloodline	support.WinUAE	2	23 February 2018 19:52
Debugging?	MartinW	Coders. C/C++	10	03 January 2018 20:59
Looking for some basic IP tools en SDK tools	Roland007	support.WinUAE	0	28 November 2012 22:34

27 June 2020, 13:53	#2
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,307	MuForce/MuGuardianAngel, Mungwall/MungList, MemSniff, PoolWatch, SegTracker, sashimi. Some are doing the same or are replacements of others but at least that is a start.

27 June 2020, 16:31	#3
Thomas Richter Registered User Join Date: Jan 2019 Location: Germany Posts: 3,300	MuForce, MuGA, Wipeout, segtracker, COP and a PC with a null-modem cable. Mungwall I can no longer recommend, replace it by Wipeout. The problem with MungWall is that it contains a crude workaround for a "feature" of the v37 layers.library that is quite disruptive with newer versions of the Os and caused some "false positives" when debugging 3.1.4. I believe the most important debugging tool for 3.1.4 was COP.

27 June 2020, 16:59	#4
walkero Registered User Join Date: May 2012 Location: Dublin/Ireland Posts: 358	Thank you guys for your reccommendations. Do you have any tips on any of these apps, or do you know a good guide on how to use any of them? This could be a good guide for any new developer like me

27 June 2020, 17:45	#5
PeterK Registered User Join Date: Apr 2005 Location: digital hell, Germany, after 1984, but worse Posts: 3,383	In addition to all those tools that were already mentioned here I'm also using LibSnooper which can report about any library function call, the register contents, the result and the task, but of course, can also be used to monitor AllocVec(), AllocMem(), AllocBitMap(), FreeVec(), FreeMem(), FreeBitMap() for example or whatever you want to know.

27 June 2020, 17:51	#6
Thomas Richter Registered User Join Date: Jan 2019 Location: Germany Posts: 3,300	In terms of system tools, there is of course SnoopDos (shows most important system tools), Xoper (shows most important system lists) and SaferPatches/ShowPatches (shows system patches). Concerning documentation: MuForce and COP come with an extensive guide/manual. For COP, there is also a tutorial in German: https://www.a1k.org/forum/index.php?threads/73115/

27 June 2020, 18:55	#7
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 2,038	COP and Snoopy. is LibSnooper better?

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)