stepping thru assembled files that are referenced as temp files ie: /tmp/ccjirvvY.s
Bill Gatliff
bgat@billgatliff.com
Sat Feb 7 01:24:00 GMT 2004
Daniel:
(gdb) display/i $pc
(gdb) stepi
(gdb) stepi
...
:^(
b.g.
Daniel Jacobowitz wrote:
>On Fri, Feb 06, 2004 at 03:49:43PM -0800, John Utz wrote:
>
>
>>Hello;
>>
>>gdb 6.0 /gdbserver is telling me that i am segfaulting in a file that
>>appears to be a tmp-name generated during the link process for the
>>parent static library.
>>
>>iblit16.s is compiled into iblit16.o and ar'd into liballd_unshared.a.
>>My exe is linked against liballd_unshared.a.
>>
>>here is what gdb says when i try to step into the problem function:
>>
>>(gdb) s
>>_linear_clear_to_color16 () at /tmp/ccjirvvY.s:27
>>27 /tmp/ccjirvvY.s: No such file or directory
>> in /tmp/ccjirvvY.s
>>Current language: auto; currently asm
>>(gdb)
>>
>>how can i tell gdb to stop looking for the tmp-name and look for this
>>function in allegro-4.0.3/src/i386/iblit16.s?
>>
>>
>
>I'm guessing it's iblit16.S, or you're arranging to run it through the
>C preprocessor some other way. If so, it's a known bug - no one's
>thought of a good solution yet.
>
>You can look at the assembly code using disassemble, for what that's
>worth.
>
>
>
More information about the Gdb
mailing list