This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
gdb/2210: 'set env' and 'shell' Underlying Environments are Different
- From: mbgdbgnu at bytnar dot net
- To: gdb-gnats at sources dot redhat dot com
- Date: 4 Dec 2006 17:38:57 -0000
- Subject: gdb/2210: 'set env' and 'shell' Underlying Environments are Different
- Reply-to: mbgdbgnu at bytnar dot net
>Number: 2210
>Category: gdb
>Synopsis: 'set env' and 'shell' Underlying Environments are Different
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon Dec 04 17:48:02 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: M. Bytnar
>Release: gdb-6.4
>Organization:
>Environment:
Fedora Core
>Description:
The 'set env' and 'shell' commands do not share the same environment.
>How-To-Repeat:
Enter these commands in GDB:
set env CURTIME=1165253337
show env CURTIME
shell date -d '1970-01-01 $CURTIME sec'
The first command works fine.
The second command works fine and displays the set value.
The third command fails, because the 'set env' and 'shell' do not share the same environment.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: