From: Denis PILAT <denis.pilat@st.com>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: gdb@sourceware.org
Subject: Re: TUI + gdbserver broken?
Date: Wed, 14 Mar 2007 11:55:00 -0000 [thread overview]
Message-ID: <45F7E28F.6060505@st.com> (raw)
In-Reply-To: <4053daab0703140242y6a401f01ga964cdf10e2766d7@mail.gmail.com>
Pedro Alves wrote:
> Denis PILAT wrote:
>>
>> Pedro Alves wrote:
>> > Hi,
>> >
>> > TUI + gdbserver seems to be broken on head. Can't reproduce when
>> > TUI + native debugging.
>> >
>> As far as the TUI is concerned:
>> It's broken with Solaris Native debugging.
>> I've spent a few hours debugging that problem but I have not solution
>> yet !!
>> I also tried using deprecated_get_selected_frame without any better
>> results :(
>>
>> This problem is present in the CVS HEAD but also in the 6.6 released
>> version, so I don't think it comes from recent changes.
>>
>
> Just tested a GNU gdb 6.6.50.20070101-cvs configured as
> sparc-sun-solaris2.9,
> built with gcc 3.4.6 I had here - TUI works fine.
>
> $uname -srvmpi
> SunOS 5.9 Generic_117171-13 sun4u sparc SUNW,Sun-Fire-480R
>
I tested 6.6 TUI configured as sparc-sun-solaris2.8 built with gcc 3.2.2.
uname gives: SunOS 5.8 Generic_117350-23 sun4u sparc
I'm looking for a 2.9 Solaris to make some tests
Denis
> Don't know if it adds any value, but I tried it under solaris xterm
> displaying on cygwin X,
> under GNU bash, version 3.2.0(1)-release (sparc-sun-solaris2.9)
>
> I'll try doing a binary search on Cygwin when I get home.
>
> Cheers,
> Pedro Alves
>
prev parent reply other threads:[~2007-03-14 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 0:58 Pedro Alves
2007-03-14 2:29 ` Daniel Jacobowitz
2007-03-17 0:48 ` Pedro Alves
2007-03-19 1:54 ` Pedro Alves
2007-03-14 9:29 ` Denis PILAT
2007-03-14 9:42 ` Pedro Alves
2007-03-14 11:55 ` Denis PILAT [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=45F7E28F.6060505@st.com \
--to=denis.pilat@st.com \
--cc=gdb@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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