Re: Auto-selecting local variable/parameters when 'p'rinting values using winedbg?
Le 12/09/2011 10:32, Frédéric Delanoy a écrit : 2011/9/12 Frédéric Delanoy: I found that --file accepts the set of commands to execute (but winedbg exits afterwards), but what does --command do? OK --command simply executes a single command and exits/continues the program until termination. Is there a way to specify initial commands to execute, then stay *inside* winedbg after the last command of the file is issued? not currently Or maybe I should use stuff like 'expect' to do that? IMO, the best solution would be to: - let winedbg have a default init command file (say .winedbgrc) to be loaded at startup (if the file exists in current directory, then in ~ directory...) - add to generic options to winedbg: + the first one to give an alternate name to default .winedbgrc file (or to locate it) + the second one to tell winedbg not to load the default file regarding the 'expect' stuff, you can look at the automaton to test winedbg https://github.com/ericZp/wdtp not sure it fully matches what you want to do, but it can help A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)
Re: Auto-selecting local variable/parameters when 'p'rinting values using winedbg?
2011/9/12 Frédéric Delanoy : > I found that --file accepts the set of commands to execute (but > winedbg exits afterwards), but what does --command do? OK --command simply executes a single command and exits/continues the program until termination. > Is there a way to specify initial commands to execute, then stay > *inside* winedbg after the last command of the file is issued? Or maybe I should use stuff like 'expect' to do that? Frédéric
Re: Auto-selecting local variable/parameters when 'p'rinting values using winedbg?
2011/9/9 Eric Pouech : > WineDbg> set ! symbol_picker scoped > will do what you want > unfortunately, there's no way to store it as a default command (you can > always use --command or --file on command line to help) > A+ Speaking of --command and --file options, they aren't documented either. I'm willing to update winedev guide, but I'd like more info first. I found that --file accepts the set of commands to execute (but winedbg exits afterwards), but what does --command do? Is there a way to specify initial commands to execute, then stay *inside* winedbg after the last command of the file is issued? Frédéric
Re: Auto-selecting local variable/parameters when 'p'rinting values using winedbg?
Le 09/09/2011 13:02, Frédéric Delanoy a écrit : 2011/9/9 Eric Pouech: WineDbg> set ! symbol_picker scoped will do what you want unfortunately, there's no way to store it as a default command (you can always use --command or --file on command line to help) Thanks for that quick response! Is there some doc on the internal commands, besides the code? http://www.winehq.org/docs/winedev-guide/dbg-config may be a bit out of date Frédéric not for that part... feel free to bring to the doc up to date set ! symbol_picker interactive being the other setting (which is the default : if several symbols found, ask the user for which one to pick) scoped meaning give precedence to local symbols over global symbols A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)
Re: Auto-selecting local variable/parameters when 'p'rinting values using winedbg?
2011/9/9 Eric Pouech : > WineDbg> set ! symbol_picker scoped > will do what you want > unfortunately, there's no way to store it as a default command (you can > always use --command or --file on command line to help) Thanks for that quick response! Is there some doc on the internal commands, besides the code? http://www.winehq.org/docs/winedev-guide/dbg-config may be a bit out of date Frédéric
