This is the mail archive of the insight@sourceware.org mailing list for the Insight project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cygwin runtime woes (was Re: [RFA] ARI fixes for gdbtk directories)


Pierre Muller wrote:
I finally managed to get one:
Can you do something with this??

This is kind of odd...


(gdb) bt
#0  error (string=0x62915c "Argument required (%s).")
    at ../../purecvs/gdb/utils.c:812
[snip]
#8  0x0041318b in catch_errors (func=0x4a15b0 <wrapped_call>,
    func_args=0x22a5b0, errstring=0x653e13 "", mask=6)
    at ../../purecvs/gdb/exceptions.c:510

Frame 8, catch_errors, should have caught any the call to frame 0. However, the question is, why is gdb_loc calling decode_line_1 with no arguments?


My memory is a little fuzzy about this, but I fired up insight on my linux box under gdb and set a breakpoint in gdb_loc. As I recall, this happens at start-up to find "main", but for some reason, it appears that the argument which should contain "main" instead contains an empty string.

Can you set a breakpoint in gdb_loc, run insight, and tell me what objc is? It should be 2, and objv[0]->bytes should be "gdb_loc" and objv[1]->bytes should be "main".

Is this not the case?

Keith


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]