From: Keith Seitz <keiths@redhat.com>
To: Bruce Korb <bruce.korb@gmail.com>
Cc: insight@sourceware.org
Subject: Re: breakpoint setting bug
Date: Tue, 23 Feb 2010 23:59:00 -0000 [thread overview]
Message-ID: <4B818472.5000101@redhat.com> (raw)
In-Reply-To: <668c430c1002211040t2c186e52o66a87ad4cd1f7f25@mail.gmail.com>
On 02/21/2010 10:40 AM, Bruce Korb wrote:
>> bug. I used your example code to try to build a test case, but I could not
>> reproduce the bug.
>
> Figured. :(
Isn't that how it always goes? O:-)
>> Was this application compiled with optimization?
>
> sharutils compiles thus:
>> gcc -DLOCALEDIR=\"/old-home/gnu/proj/sharutils-inst/share/locale\" \
>> -DHAVE_CONFIG_H -I. -I.. -I. -I.. -I../lib -I../intl -g -Wall -MT shar.o \
>> -MD -MP -MF .deps/shar.Tpo -c -o shar.o shar.c
> though I had the same symptom when adding "-O0" to the command.
I don't see anything suspicious in that, so it's definitely a bug.
>> How did you set the breakpoint?
> In the command window:
>> gdb> b emit_file_text
Okay, that makes life a lot easier: It's a gdb bug. :-)
> GNU gdb 6.8
Ah. 6.8. I don't suppose I could cajole you into trying something a
little more recent? Gdb is currently on it's 7.1 release, so you're
using something that is almost three releases behind.
FWIW, I use insight pretty much daily, and I only ever use a snapshot. I
seldom run into problems.
> I'm sure. That's the part that will take me a little time to get to....
> Sorry to just tease you. ;)
> If nothing pops up as obvious, I'll try to get to it in a week or so.
No problem. I'll be here.
Keith
prev parent reply other threads:[~2010-02-21 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 18:28 Bruce Korb
2010-02-21 18:40 ` Keith Seitz
2010-02-21 19:09 ` Bruce Korb
2010-02-23 23:59 ` Keith Seitz [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=4B818472.5000101@redhat.com \
--to=keiths@redhat.com \
--cc=bruce.korb@gmail.com \
--cc=insight@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).