How to remove the "assembler" debug window?
lazarus / 11-Options

----------------------------------------------------------------------
xaero · 2010-05-23 21:05

when your code has errors, Lazarus will notice the errors and show the
assembler window (see the gif)

how to remove the assembler debug window?

----------------------------------------------------------------------
Leledumbo · 2010-05-24 00:03

Only if it can't find the debugging info, not sure whether it can be
forced not to show though.

----------------------------------------------------------------------
99Percent · 2010-06-30 06:22

The assembler window still shows on break errors despite compiling and
linking with debug information. What am I missing? A checklist would
be appreciated.

----------------------------------------------------------------------
Marc · 2010-07-01 22:04

are there blue dots in your source code gutter ?
Does the debugger output window show errors ?

----------------------------------------------------------------------
99Percent · 2010-07-02 14:33

Quote from: Marc on July 02, 2010, 12:04:41 amare there blue dots in
your source code gutter ?yes
QuoteDoes the debugger output window show errors ?
Code: [Select]<-data-evaluate-expression BitBtn1>
&"No symbol \"BitBtn1\" in current context.\n"

^error,msg="No symbol \"BitBtn1\" in current context."

----------------------------------------------------------------------
Marc · 2010-07-07 08:29

If you have blue dots, you have line info, so the debugger is able to
find the correct line.
It is possible that your exception is in some library and that the
callstack isn't complete. In taht case you get the asm window.
Does your callstack look ok ?

----------------------------------------------------------------------
99Percent · 2010-07-08 22:46

The call stack window doesn't show blue lines for the top calls. For
example:
Code: [Select]#0 fpc_raiseexception at :0
#1 DB_DATABASEERRORFMT$ANSISTRING$array_of_const$TCOMPONENT at :0
#2 DB_TDATASET_$__FIELDBYNAME$ANSISTRING$$TFIELD at :0
#3 TFMMAIN__BUTTON1CLICK(0x380f2e8, 0x380ee78) at main.pas:98
#4 TCONTROL__CLICK(0x380f2e8) at control.inc:2227
#5 TBUTTONCONTROL__CLICK(0x380f2e8) at buttoncontrol.inc:72
#6 TCUSTOMBUTTON__CLICK(0x380f2e8) at buttons.inc:164
#7 TBUTTON__CLICK(0x380f2e8) at buttons.inc:331
#8 TBUTTONCONTROL__WMDEFAULTCLICKED({MSG = 66567, WPARAM = 5092304,
LPARAM = -591746099, RESULT = 0, WPARAMLO = 46032, WPARAMHI = 77,
LPARAMLO = 43981, LPARAMHI = 56506, RESULTLO = 0, RESULTHI = 0},
0x380f2e8) at buttoncontrol.inc:26
#9 SYSTEM_TOBJECT_$__DISPATCH$formal at :0
#10 TBUTTONCONTROL__ISCHECKEDSTORED(0x31ef750) at buttoncontrol.inc:22
Index 0 has a green arrow, index 1 and 2 have grey dots. Blue dots in
index 3 to 8, grey dot at index 9, etc

----------------------------------------------------------------------
Marc · 2010-07-12 09:01

Strange. IIRC lazarus looks at the callstack for the first location of
known source code. Just to be sure, what lazarus version do you use ?

----------------------------------------------------------------------
99Percent · 2010-07-13 04:54

I am using 0.9.28 stable build.

I am trying to get 0.9.29 svn to run, to see if I still get that
assembler window (and a strange TStringGrid OnExit bug), but running
into problems there too.