Ben,
> How about something a bit simpler like running gdb within a
'script' context,
> which will log your session to a file. Get gdb to print the variables
to the screen
> (using 'print' or whatever), wrap your data with easily searchable
characters
> (eg. ***data1 data2 data3***), then filter your data from the script
file with sed/awk
> or perl scripts?
I tried this as well and have the same GDB synchronization problem e.g.
break log_stuff
commands
silent
if (variable_logging_enabled)
printf "(%d,%d)\n",stuff1_variable,stuff2_variable
end
cont
end
The printf's don't complete before the cont happens. Sounds like maybe
this is a GDB problem...
Tim
