Re: To know the stopped reason from hook-stop

[Jim Blandy <jimb at codesourcery dot com>]

Masatake YAMATO <yamato@redhat.com> writes:
> (I am very new to this list.
>  If my topic is suitable to this list, tell me the better list.)

This list is fine, since you were posting a patch.  Given that you're
also asking broad questions about GDB's design, gdb@ would have been
okay, too.

> Is there way to know in hook-stop the reason why the execution 
> is stopped?

No. :(

> I could not find the way to do it, so I've just written a patch.
> The patch is far from complete, but I'd like to know how to improve
> it and integrate it to gdb official source tree. So I post the patch 
> here.

Hmm.

It's painful to watch people wrestle GDB's scripting language into
doing something useful.  If Daniel's patch to add Python as a
scripting language for GDB were in the public sources, then I could
say, "Don't worry about trying to fix GDB's horrible scripting
language, provide this data to Python."  I'm sure that's the better
investment.

At the same time, I don't want to make the mistake of saying, "Oh, no,
let's not commit that improvement, something much better is coming
along real soon now" when there are no specific plans for the much
better thing's arrival.

Daniel, have you had time to work on that patch since we last talked
about it?