From: Bill Gatliff <bgat@billgatliff.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: stepping thru assembled files that are referenced as temp files ie: /tmp/ccjirvvY.s
Date: Sat, 07 Feb 2004 01:24:00 -0000 [thread overview]
Message-ID: <40243E3A.7040205@billgatliff.com> (raw)
In-Reply-To: <20040206235810.GA3110@nevyn.them.org>
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.
>
>
>
prev parent reply other threads:[~2004-02-07 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 23:50 John Utz
2004-02-06 23:58 ` Daniel Jacobowitz
2004-02-07 0:32 ` Andrew Cagney
2004-02-07 1:14 ` Daniel Jacobowitz
2004-02-07 5:23 ` Ian Lance Taylor
2004-02-07 5:27 ` Daniel Jacobowitz
2004-02-07 1:24 ` Bill Gatliff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40243E3A.7040205@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox