Getting a callstack with function names, line numbers and unit names won't work if you just add the unit. Why? Because all that information is not included in your EXE by default. The madExcept IDE wizard extracts all that information automatically for you from either the map file or the debug information, zips it up and adds it to your EXE's resource section. This way creating nice callstacks with function names and line numbers suddenly becomes possible.
You can forget about all the settings, if you don't plan to use the majority of madExcept's features, anyway. You can even 99% disable madExcept's automatic exception hooking and all that clever stuff (although it's really nice), by just checking the option "activate madExcept" and "link in function names and line numbers", and by unchecking "link in madExcept code" and "link in madExcept settings". If you do that, no code is added to your EXE, just the function names and line numbers.
Next step, add madExcept.pas to your uses clause somewhere. Caution: If you add it to your dpr's uses clause, the madExcept IDE wizard will automatically remove it again, because you unchecked "link in madExcept code". You can avoid this problem by either adding it to some other unit's uses clause, or by adding the comment "// dontTouchUses" above the dpr's "uses" clause.
Now in order to get a callstack in that try..except block, you can use the following function, exported by madExcept.pas:
http://help.madshi.net/madExceptUnit.ht ... StackTrace
You can even call it without any parameters, and it will provide you with a nicely formatted callstack for the current exception.
Please note that all the above works very well for x86. But if your EXE is compiled as 64bit, things get slightly more complicated because in the moment when you reached the try..except block, parts of the information we need to create the callstack are already overwritten. So if you want all this to work in x64, you may have to fully enable madExcept (practically that means you have to activate "link in madExcept code" and "link in madExcept settings". Once you do that, madExcept will hook into the depths of the RTL to make everything work nicely for you. Even if you don't need all the fancy stuff, it usually shouldn't harm.