This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: How to portably print out Env of a Process


> X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on 
> 	elgar.sibelius.xs4all.nl
> X-Spam-Level: 
> X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed 
> 	version=3.1.1
> Date: Tue, 23 May 2006 09:16:42 +0530
> From: "Arijit Das" <arijit79@gmail.com>
> Content-Disposition: inline
> X-IsSubscribed: yes
> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
> Sender: gdb-owner@sourceware.org
> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information.
> X-UTwente-MailScanner: Found to be clean
> X-UTwente-MailScanner-SpamScore: s
> X-UTwente-MailScanner-From: gdb-return-25381-m.m.kettenis=alumnus.utwente.nl@sourceware.org
> X-XS4ALL-DNSBL-Checked: mxdrop44.xs4all.nl checked 130.89.2.8 against DNS blacklists
> X-Virus-Scanned: by XS4ALL Virus Scanner
> X-XS4ALL-Spam-Score: 0.401 () FROM_ENDS_IN_NUMS,HTML_MESSAGE
> X-XS4ALL-Spam: NO
> Envelope-To: mark.kettenis@xs4all.nl
> X-MIME-Autoconverted: from quoted-printable to 8bit by mxdrop44.xs4all.nl id k4N3lNcQ019572
> X-UIDL: 1148356045._smtp.mxdrop44.19580,S=3409
> 
> Hi,
> 
> Is it possible to print out the env of a process portably with the
> same cmdline/script in different os/arch combinations?
> 
> Here is how I tried to do it for i686 - RH3.0:
> 
> (gdb) p (char *) getenv("HOME")
> [Switching to Thread 1024 (LWP 17639)]
> $1 = 0xdffff781 "/remote/vtghome7/arijit"
> (gdb)
> 
> It worked fine.
> 
> But when I tried executing this command in x86_64, I got strange results:
> 
> (gdb) p (char *) getenv("HOME")
> [Switching to Thread 182901576896 (LWP 26427)]
> $1 = 0xffffffffbfffc790 <Address 0xffffffffbfffc790 out of bounds>
> (gdb)
> 
> I guess some kind of 32/64 bits conversion might be messing things up
> here....but am not sure exactly what? Any help here?
> 

Make sure you install libc with full debug info.  It looks like you're
using Linux.  Debian has packages with the necessary debug info.
Other distros might not.  If your distro does not provide such
packages please complain.

Cheers,

Mark


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]