Re: might a bug in ido-mode

[Eli Zaretskii]

> From: zwz <address@hidden>
> Date: Tue, 27 Apr 2010 16:21:29 +0800
> 
> Thread 1 (thread 4136.0xea8):
> #0  0x77cf5e74 in ntdll!LdrAccessResource ()
>     from C:\windows\system32\ntddl.dll
> #1  0x764a6fd1 in USER32!SetMenuContextHelpId ()
>     from C:\windows\system32\user32.dll
> #2  0x0116e2fe in set_frame_menubar ()
> #3  0x010178ef in update_menu_bar ()
> #4  0x0102ad6a in prepare_menu_bars ()
> #5  0x0102ed02 in redisplay_internal ()
> #6  0x01061d66 in read_char ()
> #7  0x01063334 in read_key_sequence.clone.0 ()
> #8  0x01065bd0 in command_loop_1 ()
> #9  0x0100a592 in internal_condition_case ()
> #10 0x0105bebf in command_loop_2 ()
> #11 0x0100a4dc in internal_catch ()
> #12 0x0105c848 in command_loop ()
> #13 0x0105c8d3 in recursive_edit_1 ()
> #14 0x0104c8ce in Frecursive_edit ()
> #15 0x01002d86 in main ()

This thread (thread 1) is the one we are interested in.  But why
doesn't the backtrace include function arguments?  Did you strip some
of the debugging info or something?

What does this show:

  (gdb) thread 1
  (gdb) bt 5 full

> p.s. Is there anyway to print the backtract to a file?

Yes, say "set logging on" before "bt", and then all output will be ion
the file gdb.txt.