Discussion list for gdb, the GNU source debugger

StevieB | 1 Apr 2008 13:37

Debugging shared object modules with GDB


I am relatively inexperienced with the intracacies of Linux Shared Objects,
but need to do the following;

I have a test system running on Linux with a shared module that I need to
debug. How can I create and debug a version of this module.

I am thinking about adding a main() to the module with an endless loop. Then
compile, and run it. I'll add a break on the function I need to debug, then
run it.

What I am not sure is how to 'unload' the existing module, so my debugged
version will be used.

Am I heading in the right direction, or is there a better way?

Many thanks in anticipation
--

-- 
View this message in context: http://www.nabble.com/Debugging-shared-object-modules-with-GDB-tp16418171p16418171.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

headers

Hezi Sasson | 2 Apr 2008 23:44

RE: Debugging shared object modules with GDB

please remove me from the list

From: gdb-bounces+hezi=netwise.co.il <at> gnu.org on behalf of StevieB
Sent: Tue 4/1/2008 1:37 PM
To: Gdb <at> gnu.org
Subject: Debugging shared object modules with GDB

I am relatively inexperienced with the intracacies of Linux Shared Objects,
but need to do the following;

I have a test system running on Linux with a shared module that I need to
debug. How can I create and debug a version of this module.

I am thinking about adding a main() to the module with an endless loop. Then
compile, and run it. I'll add a break on the function I need to debug, then
run it.

What I am not sure is how to 'unload' the existing module, so my debugged
version will be used.

Am I heading in the right direction, or is there a better way?

Many thanks in anticipation
--
View this message in context: http://www.nabble.com/Debugging-shared-object-modules-with-GDB-tp16418171p16418171.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

headers

StevieB | 3 Apr 2008 10:17

RE: Debugging shared object modules with GDB


I'm sorry I don't understand what you mean. I haven't added you to any lists.

Have you been receiving emails regarding this post?

Hezi Sasson wrote:
> 
> please remove me from the list
> 
> ________________________________
> 
> From: gdb-bounces+hezi=netwise.co.il <at> gnu.org on behalf of StevieB
> Sent: Tue 4/1/2008 1:37 PM
> To: Gdb <at> gnu.org
> Subject: Debugging shared object modules with GDB
> 
> 
> 
> 
> I am relatively inexperienced with the intracacies of Linux Shared
> Objects,
> but need to do the following;
> 
> I have a test system running on Linux with a shared module that I need to
> debug. How can I create and debug a version of this module.
> 
> I am thinking about adding a main() to the module with an endless loop.
> Then
> compile, and run it. I'll add a break on the function I need to debug,
> then
> run it.
> 
> What I am not sure is how to 'unload' the existing module, so my debugged
> version will be used.
> 
> Am I heading in the right direction, or is there a better way?
> 
> Many thanks in anticipation
> --
> View this message in context:
> http://www.nabble.com/Debugging-shared-object-modules-with-GDB-tp16418171p16418171.html
> Sent from the Gnu - gdb - General mailing list archive at Nabble.com.
> 
> 
> 
> 
> 
> 
> 
> 
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer
> viruses.
> ************************************************************************************
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer
> viruses.
> ************************************************************************************
> 
> 
> 
> 

--

-- 
View this message in context: http://www.nabble.com/Debugging-shared-object-modules-with-GDB-tp16418171p16467309.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

headers

Hezi Sasson | 3 Apr 2008 10:54

RE: Debugging shared object modules with GDB

yes

and i would like to unsubscibe

thank you

From: gdb-bounces+hezi=netwise.co.il <at> gnu.org on behalf of StevieB
Sent: Thu 4/3/2008 10:17 AM
To: Gdb <at> gnu.org
Subject: RE: Debugging shared object modules with GDB

I'm sorry I don't understand what you mean. I haven't added you to any lists.

Have you been receiving emails regarding this post?

Hezi Sasson wrote:
>
> please remove me from the list
>
> ________________________________
>
> From: gdb-bounces+hezi=netwise.co.il <at> gnu.org on behalf of StevieB
> Sent: Tue 4/1/2008 1:37 PM
> To: Gdb <at> gnu.org
> Subject: Debugging shared object modules with GDB
>
>
>
>
> I am relatively inexperienced with the intracacies of Linux Shared
> Objects,
> but need to do the following;
>
> I have a test system running on Linux with a shared module that I need to
> debug. How can I create and debug a version of this module.
>
> I am thinking about adding a main() to the module with an endless loop.
> Then
> compile, and run it. I'll add a break on the function I need to debug,
> then
> run it.
>
> What I am not sure is how to 'unload' the existing module, so my debugged
> version will be used.
>
> Am I heading in the right direction, or is there a better way?
>
> Many thanks in anticipation
> --
> View this message in context:
> http://www.nabble.com/Debugging-shared-object-modules-with-GDB-tp16418171p16418171.html
> Sent from the Gnu - gdb - General mailing list archive at Nabble.com.
>
>
>
>
>
>
>
>
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer
> viruses.
> ************************************************************************************
>
>
>
>
>
>
>
>
>
>
>
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer
> viruses.
> ************************************************************************************
>
>
>
>

--
View this message in context: http://www.nabble.com/Debugging-shared-object-modules-with-GDB-tp16418171p16467309.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

headers

Ignacio Castaño | 6 Apr 2008 01:25

Re: Debugging shared object modules with GDB

Hezi,

I think that none of the subscribers can do anything about your
problem. This is not the first time you contact the mailing asking to
be unsubscribed. Don't you realize that the only thing you accomplish
is to annoy the other members?

I would like to unsubscribe as much as you do:

http://www.nabble.com/problems-unsubscribing-to15428668.html

but spamming the list is not the way to go. I've also tried to contact
the GNU project at: gnu <at> gnu.org, but I got no response. Do you suggest
other way of action?

-- 
Ignacio Castaño
castano <at> gmail.com

On Thu, Apr 3, 2008 at 1:54 AM, Hezi Sasson <hezi <at> netwise.co.il> wrote:
>
>
>
> yes
> and i would like to unsubscibe
> thank you
>
>  ________________________________
>
> From: gdb-bounces+hezi=netwise.co.il <at> gnu.org on behalf of StevieB
> Sent: Thu 4/3/2008 10:17 AM
> To: Gdb <at> gnu.org
> Subject: RE: Debugging shared object modules with GDB
>
>
>
>
>
>
> I'm sorry I don't understand what you mean. I haven't added you to any
> lists.
>
> Have you been receiving emails regarding this post?
>
>
>
> Hezi Sasson wrote:
> >
> > please remove me from the list
> >
> > ________________________________
> >
> > From: gdb-bounces+hezi=netwise.co.il <at> gnu.org on behalf of StevieB
> > Sent: Tue 4/1/2008 1:37 PM
> > To: Gdb <at> gnu.org
> > Subject: Debugging shared object modules with GDB
> >
> >
> >
> >
> > I am relatively inexperienced with the intracacies of Linux Shared
> > Objects,
> > but need to do the following;
> >
> > I have a test system running on Linux with a shared module that I need to
> > debug. How can I create and debug a version of this module.
> >
> > I am thinking about adding a main() to the module with an endless loop.
> > Then
> > compile, and run it. I'll add a break on the function I need to debug,
> > then
> > run it.
> >
> > What I am not sure is how to 'unload' the existing module, so my debugged
> > version will be used.
> >
> > Am I heading in the right direction, or is there a better way?
> >
> > Many thanks in anticipation