From: leiming <blackhorse_linux@sina.com>
To: gdb@sources.redhat.com
Cc: biswapesh_chatterjee@tcscal.co.in
Subject: RE: Re: how to use libgdb ?
Date: Thu, 19 Sep 2002 01:04:00 -0000 [thread overview]
Message-ID: <20020919080031.17164.qmail@sina.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3066 bytes --]
hi!
Thank you!
If I want to build my GUI IDE in cygwin+win2000 ,is your approach
right to finish it?
leiming
<blackhorse_linux@sina.com>
----- Original Message -----
From:Biswapesh Chattopadhyay <biswapesh_chatterjee@tcscal.co.in>
To:GDB List <gdb@sources.redhat.com>
Subject:Re: how to use libgdb ?
Date:Thu, 19 Sep 2002 12:38:40 +0800
>Hi list
>
>I'm one of the developers of Anjuta (http://anjuta.sf.net/), an IDE for
>GNOME. Currently, we are using a spawned subprocess for GDB interaction.
>This works fairly well, but obviously a shared library with a nice (and
>reasoinably stable) API would be very helpful for IDE developers. So, my
>question is: if GDB build process already builds libgdb.a, would any
>patches to make it build a shared libgdb.so be accepted into the main
>tree ? It might be very useful, for example, for gnome-debug, which is
>an upcoming component for debugging applications using a nice GUI
>interface. This might speed up the responsiveness and enable us to do
>more advanced stuff (such as tracing multiple threads simultaneously).
>
>Plug: If you are on Linux, please try out Anjuta CVS - you can debug
>Anjuta using Anjuta and the debugger interface is really nice !
>
>Thanks in advance.
>Biswa.
>
>
>> Well,
>> there really is no libgdb at this point.
>> There has been some talk of one by developers as something they'd
>> eventually like to do, but right not there is nothing available.
>>
>> However, the gdb build process (at least on linux) created libgdb.a
>> and then builds main.c with that to create gdb. It is possible to
>> create libgdb.so rather than libgdb.a and dynamically link to the new
>> library. It just takes some fiddling with the Makefile that configure
>> created.
>> I've not done extensive testing on it, but it seems to work for me.
>> If you wanted to build your own app on that, you could get sample usage
>> from the main.c file
>>
>> I guess it should be pointed out, though, that the libgdb.so that you
>> create is a GPL'd work, so even dynamically linking to it then requires
>> that you GPL your application as well.
>>
>> Scott Moser
>> Software Engineer; Linux Technology Center
>> IBM Corp., Austin, Tx
>> (512) 838-1533 T/L: 678-1533
>> ssmoser@us.ibm.com , internal zip: 9812
>>
>> On Wed, 18 Sep 2002, leiming wrote:
>>
>> >
>> > hi!
>> > Who has used libgdb to integrate gdb into GUI developement?
>> > Can you tell me the detailed step or provide some manual?
>> >
>> > Thanks a lot!
>> >
>> > leiming
>> > <blackhorse_linux@sina.com>
>> >
>>
>>
>
>
>
>
______________________________________
===================================================================
ÐÂÀËÃâ·Ñµç×ÓÓÊÏä (http://mail.sina.com.cn)
ÐÂÀ˶þÊÖÊг¡£ºÒ»ÔªÍ¶È룬ʮ·Ö¾ªÏ²£¬°Ù·ÖÂúÒâ (http://classad.sina.com.cn/2shou/)
ÊýÍòÕÅÊÖ»úͼƬÊýÍòÊ×¶ÌÐÅÁåÉùÈÎÄãÌôÑ¡£¬Ã¿Ìì¶¼ÓиüР(http://sms.sina.com.cn/cgi-bin/sms/smspic.cgi)
next reply other threads:[~2002-09-19 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 1:04 leiming [this message]
2002-09-19 1:58 ` Biswapesh Chattopadhyay
2002-09-22 19:51 leiming
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=20020919080031.17164.qmail@sina.com \
--to=blackhorse_linux@sina.com \
--cc=biswapesh_chatterjee@tcscal.co.in \
--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