[Bug python/13642] New: merge --python command-line option

[tromey at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=13642

Bug #: 13642
Summary: merge --python command-line option
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: python
AssignedTo: ***@sourceware.org
ReportedBy: ***@redhat.com
Classification: Unclassified


We should merge the --python command-line option from
archer-tromey-python.
Real-world use for it:
http://blog.scottt.tw/2012/01/exploring-gdb-python-api-with-ipython_31.html

[tromey at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=13642

Tom Tromey <tromey at redhat dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED

--- Comment #1 from Tom Tromey <tromey at redhat dot com> ---
To my surprise it seems that this option is not needed -- "-x" does the job.

bapiya. cat > q.py
print "Hi Bob"
bapiya. gdb --batch -x q.py
Hi Bob


I learned this thanks to Debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681533

[palves at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=13642

Pedro Alves <palves at redhat dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com

--- Comment #2 from Pedro Alves <palves at redhat dot com> ---
For completeness, just adding a comment to mention that it would still be
needed if we wanted to support users that have "set script-extension off" in
their .gdbinit:

(gdb) help set script-extension strict
Set mode for script filename extension recognition.
off == no filename extension recognition (all sourced files are GDB scripts)
soft == evaluate script according to filename extension, fallback to GDB
script
strict == evaluate script according to filename extension, error if not
supported

[tromey at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=13642

Tom Tromey <tromey at redhat dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---

--- Comment #3 from Tom Tromey <tromey at redhat dot com> ---
(In reply to Pedro Alves from comment #2)

Post by palves at redhat dot com
For completeness, just adding a comment to mention that it would still be
needed if we wanted to support users that have "set script-extension off" in

Yeah; though I am not particularly sympathetic to those users.
Actually it seems somewhat wrong to me that --batch does not imply -nx.
Perhaps we need a new option that is like "--batch -nx -x" all in one.
Emacs uses "--script" for this.

Reopening.

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=13642

Tom Tromey <tromey at sourceware dot org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
Summary|merge --python command-line |add --script command-line
|option |option

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
Repurposing.