Skip Montanaro wrote: > There's one slight hitch. It works perfectly when travelling up the C stack > using the up command, however in my environment at least (MacOSX w/ Apple's > gcc and gdb) it causes gdb to segfault when travelling down the stack. I > can't see anything that would make the behavior different going up instead > of down. I need some people to try this thing out to see if it barfs for > them as well. Maybe it's just something peculiar to my environment. OTOH, > perhaps it's a bug in gdb. Without actually looking at your code: a segfault in gdb is always a bug, even if triggered through gdb macros. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4