* Building GDB 6.1 for SH target
@ 2004-05-25 15:41 Julian Back
2004-05-26 1:31 ` Daniel Jacobowitz
0 siblings, 1 reply; 6+ messages in thread
From: Julian Back @ 2004-05-25 15:41 UTC (permalink / raw)
To: gdb
I've started using GDB 6.1 with an SH target as I wanted to have support
for SH4A. When I build GDB 6.1 for a target of "sh-linux" (which I used
fine with GDB 6.0) I get a warning message when I run GDB:
warning: A handler for the OS ABI "GNU/Linux" is not built into this
configuration
of GDB. Attempting to continue with the default sh settings.
GDB then appears to work OK.
When I build GDB with a target of just "sh" I don't get this warning but
then I don't get support for ELF binaries either.
At the moment I don't actually need Linux support (but I probably will
in the future), but I do need ELF support. I can live with the warning
but I will want to distribute the GDB binary to others so I'd prefer to
avoid it.
I could just remove the warning from the source, but what would be the
correct way to fix this? I would also be interested to know why GDB no
longer seems to have Linux support for SH.
Thanks
Julian Back
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Building GDB 6.1 for SH target
2004-05-25 15:41 Building GDB 6.1 for SH target Julian Back
@ 2004-05-26 1:31 ` Daniel Jacobowitz
2004-05-26 11:30 ` Julian Back
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Jacobowitz @ 2004-05-26 1:31 UTC (permalink / raw)
To: Julian Back; +Cc: gdb
On Tue, May 25, 2004 at 04:41:09PM +0100, Julian Back wrote:
> I've started using GDB 6.1 with an SH target as I wanted to have support
> for SH4A. When I build GDB 6.1 for a target of "sh-linux" (which I used
> fine with GDB 6.0) I get a warning message when I run GDB:
>
> warning: A handler for the OS ABI "GNU/Linux" is not built into this
> configuration
> of GDB. Attempting to continue with the default sh settings.
>
> GDB then appears to work OK.
>
> When I build GDB with a target of just "sh" I don't get this warning but
> then I don't get support for ELF binaries either.
>
> At the moment I don't actually need Linux support (but I probably will
> in the future), but I do need ELF support. I can live with the warning
> but I will want to distribute the GDB binary to others so I'd prefer to
> avoid it.
>
> I could just remove the warning from the source, but what would be the
> correct way to fix this? I would also be interested to know why GDB no
> longer seems to have Linux support for SH.
No one's updated the GDB sh-linux port in a long time, and GDB has
evolved out from under it.
--
Daniel Jacobowitz
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Building GDB 6.1 for SH target
2004-05-26 1:31 ` Daniel Jacobowitz
@ 2004-05-26 11:30 ` Julian Back
2004-05-26 11:57 ` shared library memory leak MuthuKumar-15
2004-05-26 12:48 ` Building GDB 6.1 for SH target Daniel Jacobowitz
0 siblings, 2 replies; 6+ messages in thread
From: Julian Back @ 2004-05-26 11:30 UTC (permalink / raw)
To: Daniel Jacobowitz; +Cc: gdb
Daniel Jacobowitz wrote:
>On Tue, May 25, 2004 at 04:41:09PM +0100, Julian Back wrote:
>
>
>>I could just remove the warning from the source, but what would be the
>>correct way to fix this? I would also be interested to know why GDB no
>>longer seems to have Linux support for SH.
>>
>>
>
>No one's updated the GDB sh-linux port in a long time, and GDB has
>evolved out from under it.
>
>
I realise that. My immediate problem has been solved by recompiling GDB
with a target of "sh-elf". I would be interested to know of any
specific changes I could make to reinstate the sh-linux port.
Thanks
Julian
^ permalink raw reply [flat|nested] 6+ messages in thread
* shared library memory leak
2004-05-26 11:30 ` Julian Back
@ 2004-05-26 11:57 ` MuthuKumar-15
2004-05-26 12:48 ` Building GDB 6.1 for SH target Daniel Jacobowitz
1 sibling, 0 replies; 6+ messages in thread
From: MuthuKumar-15 @ 2004-05-26 11:57 UTC (permalink / raw)
To: gdb
hai all.
Is it good to find the memory leaks in the shared libraries using GDB ?
How to use the GDB for thread debugging on HP-UX platform ?
Regards,
Muthukumar.
---
=============== It is a "Virus Free Mail" ===============
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.690 / Virus Database: 451 - Release Date: 5/22/2004
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Building GDB 6.1 for SH target
2004-05-26 11:30 ` Julian Back
2004-05-26 11:57 ` shared library memory leak MuthuKumar-15
@ 2004-05-26 12:48 ` Daniel Jacobowitz
2004-05-26 16:56 ` Julian Back
1 sibling, 1 reply; 6+ messages in thread
From: Daniel Jacobowitz @ 2004-05-26 12:48 UTC (permalink / raw)
To: Julian Back; +Cc: gdb
On Wed, May 26, 2004 at 12:30:29PM +0100, Julian Back wrote:
> Daniel Jacobowitz wrote:
>
> >On Tue, May 25, 2004 at 04:41:09PM +0100, Julian Back wrote:
> >
> >
> >>I could just remove the warning from the source, but what would be the
> >>correct way to fix this? I would also be interested to know why GDB no
> >>longer seems to have Linux support for SH.
> >>
> >>
> >
> >No one's updated the GDB sh-linux port in a long time, and GDB has
> >evolved out from under it.
> >
> >
> I realise that. My immediate problem has been solved by recompiling GDB
> with a target of "sh-elf". I would be interested to know of any
> specific changes I could make to reinstate the sh-linux port.
Take a look at the osabi sniffers used by some other targets; SH needs
to register one, and that will fix the warning. I don't know if it
needs to do anything.
If you're interested in working on the SH port, will you be able to
file a copyright assignment?
--
Daniel Jacobowitz
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Building GDB 6.1 for SH target
2004-05-26 12:48 ` Building GDB 6.1 for SH target Daniel Jacobowitz
@ 2004-05-26 16:56 ` Julian Back
0 siblings, 0 replies; 6+ messages in thread
From: Julian Back @ 2004-05-26 16:56 UTC (permalink / raw)
To: Daniel Jacobowitz; +Cc: gdb
Daniel Jacobowitz wrote:
>On Wed, May 26, 2004 at 12:30:29PM +0100, Julian Back wrote:
>
>
>>with a target of "sh-elf". I would be interested to know of any
>>specific changes I could make to reinstate the sh-linux port.
>>
>>
>
>Take a look at the osabi sniffers used by some other targets; SH needs
>to register one, and that will fix the warning. I don't know if it
>needs to do anything.
>
>If you're interested in working on the SH port, will you be able to
>file a copyright assignment?
>
>
Yes, that shouldn't be a problem. I can't guarantee to achieve anything
useful though!
Julian
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-05-26 16:56 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-05-25 15:41 Building GDB 6.1 for SH target Julian Back
2004-05-26 1:31 ` Daniel Jacobowitz
2004-05-26 11:30 ` Julian Back
2004-05-26 11:57 ` shared library memory leak MuthuKumar-15
2004-05-26 12:48 ` Building GDB 6.1 for SH target Daniel Jacobowitz
2004-05-26 16:56 ` Julian Back
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox