Support.Bugs History

Hide minor edits - Show changes to markup

December 16, 2012, at 01:30 AM by ban - Fix various typos and use better formatting
Changed line 1 from:

If you think found a bug in Geany or if you have a feature request, please file bugs at the Sourceforge.net bug tracker and features on the Sourceforge.net feature tracker.

to:

If you think you found a bug in Geany or if you have a feature to request, please file bugs at the Sourceforge.net bug tracker and features on the Sourceforge.net feature tracker.

Changed lines 5-6 from:

It would help a lot if you register at the Sourceforge.net account system and log in then. This gives you the advantage that you are notified by email when we need to ask you any questions about your request. Sometimes we need to rename the title of a request, so using a login means you won't lose track of what happens to it.

to:

It would help a lot if you register at the Sourceforge.net account system and log in then. This allows you to be notified when we need to ask for further details about your request, as well as when it's addressed. Sometimes we also need to rename the title of a report, so using a login means you won't lose track of what happens to your report.

Changed lines 20-21 from:

Geany prints useful information on the command-line when run with the -v switch. This can be useful in diagnosing a bug.

to:

Geany prints useful information on the command-line when run with the -v switch. This can be useful to diagnose a bug.

Changed lines 25-26 from:

If Geany crashed, it would also help us a lot if you can give us a backtrace with made using gdb:

to:

If Geany crashed, it would also help us a lot if you can give us a backtrace made using gdb:

Changed line 28 from:
  • Type run -v (followed by any command-line arguments you used with Geany when the bug occurred)
to:
  • Type run -v (followed by any command-line arguments you used with Geany when the bug occurred) in the gdb prompt
Changed lines 36-45 from:

1. Get a backtrace from a debug package of Geany (if your distro has one) or
2. Get a backtrace from a fresh Geany build with appropriate debug flags:

  • make clean
  • ./configure CFLAGS=-g
  • Then build Geany with make, etc.

This also prevents optimization flags (usually enabled e.g. -O2) from inlining static functions where the bug might be hiding.

Note: a default source configure with gcc should include the -g debug flag, but on some systems CFLAGS is already set either by autoconf or in the shell environment, so it may need overriding.

to:
  1. Get a backtrace from a debug package of Geany (if your distro has one) or
  2. Get a backtrace from a fresh Geany build with appropriate debug flags:
    • make clean
    • ./configure CFLAGS=-g
    • Then build Geany with make, etc.
    This also prevents optimization flags (usually enabled e.g. -O2) from inlining static functions where the bug might be hiding.
    Note: a default source configure with gcc should include the -g debug flag, but on some systems CFLAGS is already set either by autoconf or in the shell environment, so it may need overriding.
November 03, 2011, at 03:00 PM by nick - add note about reporting filetype
Changed lines 17-18 from:
to:
  1. The filetype the bug occurred with (if applicable)
September 28, 2010, at 12:36 PM by nick - try to make backtrace info a bit clearer
Changed lines 26-27 from:
  • Run gdb /path/to/geany
  • Type run followed by any command-line arguments you used with Geany when the bug occurred
to:
  • Run gdb /path/to/geany (Note: the usual path can be found by running which geany)
  • Type run -v (followed by any command-line arguments you used with Geany when the bug occurred)
February 15, 2010, at 05:46 PM by dmaphy - consistently use headings
Changed line 4 from:

SourceForge bug tracker

to:

SourceForge bug tracker

Changed line 18 from:

Other useful information

to:

Other useful information

Changed line 23 from:

Getting a backtrace

to:

Getting a backtrace

February 15, 2010, at 02:34 PM by dmaphy - small rework of text and links
Changed lines 1-2 from:

If you found a bug in Geany or have a feature request, please use the bug or request tracking system on Sourceforge.net or write a mail to the mailing list.

to:

If you think found a bug in Geany or if you have a feature request, please file bugs at the Sourceforge.net bug tracker and features on the Sourceforge.net feature tracker. You can also feel free to subscribe and write to our mailing list.

Changed lines 5-6 from:

When using the SourceForge bug tracker it helps a lot if you log in so that you are notified by email if we need to ask you any questions about the bug/request. Sometimes we need to rename the bug/request, so using a login means you won't lose track of what happens to it. You can register here.

to:

It would help a lot if you register at the Sourceforge.net account system and log in then. This gives you the advantage that you are notified by email when we need to ask you any questions about your request. Sometimes we need to rename the title of a request, so using a login means you won't lose track of what happens to it.

Changed lines 9-12 from:

If you want to add a feature request, click here.

For the bug tracking system, click here.

to:
  • Sourceforge.net bug tracker
  • Sourceforge.net feature tracker
Changed lines 21-22 from:

Sometimes you might find a bug that only occurs with a certain configuration - in this case it can be helpful if you send us your ~/.geany/geany.conf file (where ~ is your home directory).

to:

Sometimes you might find a bug that only occurs with a certain configuration - in this case it can be helpful if you send us your ~/.geany/geany.conf and any other concerned configuration file. (where ~ is your home directory).

Changed lines 24-25 from:

If Geany crashed/segfaulted, it will also help us if you can give us a backtrace with gdb:

to:

If Geany crashed, it would also help us a lot if you can give us a backtrace with made using gdb:

Changed lines 33-34 from:

Sometimes the backtrace is not so useful if Geany was built without debug information, or useful information was removed by using -fomit-frame-pointer or by stripping the binary (but it may still be worth sending it to us). In this case it would be great if you could either:

to:

In some cases the backtrace may not be that useful. This mostly happens when Geany was built without debug information, useful information was removed by using -fomit-frame-pointer or the binary was stripped (but it may still be worth sending it to us). In this case it would be great if you could either:

November 12, 2009, at 01:21 PM by nick - Use -V for version info
Changed line 15 from:
  1. The version number of GTK+ (can be printed with geany -v)
to:
  1. The version number of GTK+ (can be printed with geany -V)
November 12, 2009, at 01:19 PM by nick - -v isn't always enabled for svn version
Changed lines 19-20 from:

Geany prints useful information on the command-line when run with the -v switch (which is always enabled if you're using the SVN version). This can be useful in diagnosing a bug.

to:

Geany prints useful information on the command-line when run with the -v switch. This can be useful in diagnosing a bug.

November 12, 2009, at 01:06 PM by nick - Add note about distro debug packages
Changed lines 33-34 from:

Sometimes the backtrace is not so useful if Geany was built without debug information, or useful information was removed by using -fomit-frame-pointer or by stripping the binary (but it may still be worth sending it to us). In this case it would be great if you could get a backtrace from a fresh Geany build with appropriate debug flags:

to:

Sometimes the backtrace is not so useful if Geany was built without debug information, or useful information was removed by using -fomit-frame-pointer or by stripping the binary (but it may still be worth sending it to us). In this case it would be great if you could either:

1. Get a backtrace from a debug package of Geany (if your distro has one) or
2. Get a backtrace from a fresh Geany build with appropriate debug flags:

November 12, 2009, at 12:56 PM by nick - Add note about disabling optimization being useful for debugging
Changed lines 33-34 from:

Sometimes the backtrace is not so useful if Geany was built without debug information, or useful information was removed by using -fomit-frame-pointer or by stripping the binary (but it's still worth sending it to us). In this case it would be great if you could get a backtrace from a fresh Geany build with appropriate debug flags:

to:

Sometimes the backtrace is not so useful if Geany was built without debug information, or useful information was removed by using -fomit-frame-pointer or by stripping the binary (but it may still be worth sending it to us). In this case it would be great if you could get a backtrace from a fresh Geany build with appropriate debug flags:

Changed lines 39-41 from:

Note: a default source configure should include the -g debug flag, but on some systems CFLAGS is already set either by autoconf or in the shell environment, so it may need overriding.

to:

This also prevents optimization flags (usually enabled e.g. -O2) from inlining static functions where the bug might be hiding.

Note: a default source configure with gcc should include the -g debug flag, but on some systems CFLAGS is already set either by autoconf or in the shell environment, so it may need overriding.

March 31, 2009, at 06:36 PM by enrico - s/-d/-v/
Changed line 15 from:
  1. The version number of GTK+ (can be printed with geany -d)
to:
  1. The version number of GTK+ (can be printed with geany -v)
Changed lines 19-20 from:

Geany prints useful information on the command-line when run with the -d switch (which is always enabled if you're using the SVN version). This can be useful in diagnosing a bug.

to:

Geany prints useful information on the command-line when run with the -v switch (which is always enabled if you're using the SVN version). This can be useful in diagnosing a bug.

August 13, 2008, at 03:59 PM by nick - edit for clarity
Changed lines 6-7 from:
Please do not submit bugs/requests for plugins not distributed with Geany here - see the Plugins page.
to:
Please do not submit bugs/enhancement requests for outside plugins here - see the Plugins page.
July 08, 2008, at 11:05 AM by nick - add note about not submitting external plugin bugs here
Added lines 6-7:
Please do not submit bugs/requests for plugins not distributed with Geany here - see the Plugins page.
March 28, 2008, at 04:30 PM by nick - add sf.net heading, and link to register
Added lines 3-5:

SourceForge bug tracker

When using the SourceForge bug tracker it helps a lot if you log in so that you are notified by email if we need to ask you any questions about the bug/request. Sometimes we need to rename the bug/request, so using a login means you won't lose track of what happens to it. You can register here.

Deleted lines 9-10:

When using SourceForge it would help if you use a login so that you are notified by email if we need to ask you any questions about the bug report.

March 28, 2008, at 04:22 PM by nick - edit: default CFLAGS may be set by autoconf
Changed line 35 from:

Note: a default source configure should include the -g debug flag, but on some systems CFLAGS is already set in the shell environment and may need overriding. (You can use echo $CFLAGS to find out.)

to:

Note: a default source configure should include the -g debug flag, but on some systems CFLAGS is already set either by autoconf or in the shell environment, so it may need overriding.

March 20, 2007, at 04:54 PM by nick - group bug reports section, move other info section up
Changed lines 5-9 from:

For the bug tracking system of SourceForge.net, click here.

Please try to give us reliable instructions to reproduce the bug, so we can diagnose the cause. When using SourceForge it would help if you use a login so that you are notified by email if we need to ask you any questions about the bug report.

Getting a backtrace

to:

For the bug tracking system, click here.

When using SourceForge it would help if you use a login so that you are notified by email if we need to ask you any questions about the bug report.

Bug reports

Please try to give us reliable instructions to reproduce the bug, so we can diagnose the cause. We also need:

  1. The version number of Geany
  2. The version number of GTK+ (can be printed with geany -d)
  3. Your OS details

Other useful information

Geany prints useful information on the command-line when run with the -d switch (which is always enabled if you're using the SVN version). This can be useful in diagnosing a bug.

Sometimes you might find a bug that only occurs with a certain configuration - in this case it can be helpful if you send us your ~/.geany/geany.conf file (where ~ is your home directory).

Getting a backtrace

Deleted lines 35-39:

Other useful information

Sometimes you might find a bug that only occurs with a certain configuration - in this case it would be helpful if you send us your ~/.geany/geany.conf file (where ~ is your home directory).

Besides a backtrace, Geany prints useful information on the command-line when run with the -d switch (which is always enabled if you're using the SVN version). This can also be useful in diagnosing a bug.

March 20, 2007, at 04:35 PM by nick - Add note about overriding shell CFLAGS for a debug build
Changed lines 24-25 from:

Note: a default source configure should include the -g debug flag.

to:

Note: a default source configure should include the -g debug flag, but on some systems CFLAGS is already set in the shell environment and may need overriding. (You can use echo $CFLAGS to find out.)

August 19, 2006, at 10:30 AM by nick - Added Other useful information section
Changed lines 7-8 from:

Please try to give us reliable instructions to reproduce the bug, so we can diagnose the cause. It would also help if you use a Sourceforge login so that you are notified by email if we need to ask you any questions about the bug report.

to:

Please try to give us reliable instructions to reproduce the bug, so we can diagnose the cause. When using SourceForge it would help if you use a login so that you are notified by email if we need to ask you any questions about the bug report.

Getting a backtrace

Changed line 19 from:

Sometimes the backtrace is not useful if Geany was built without debug information, or useful information was removed by using -fomit-frame-pointer or by stripping the binary. In this case it would be great if you could get a backtrace from a fresh Geany build with appropriate debug flags:

to:

Sometimes the backtrace is not so useful if Geany was built without debug information, or useful information was removed by using -fomit-frame-pointer or by stripping the binary (but it's still worth sending it to us). In this case it would be great if you could get a backtrace from a fresh Geany build with appropriate debug flags:

Changed lines 24-29 from:

Note: a default source configure should include the -g debug flag.

to:

Note: a default source configure should include the -g debug flag.

Other useful information

Sometimes you might find a bug that only occurs with a certain configuration - in this case it would be helpful if you send us your ~/.geany/geany.conf file (where ~ is your home directory).

Besides a backtrace, Geany prints useful information on the command-line when run with the -d switch (which is always enabled if you're using the SVN version). This can also be useful in diagnosing a bug.

August 18, 2006, at 04:57 PM by nick - Added more info about bug reports and getting a backtrace
Changed lines 1-2 from:

If you found a bug in Geany or have a feature request, please use the bug tracking system on Sourceforge.net or write a mail to the mailing list.

to:

If you found a bug in Geany or have a feature request, please use the bug or request tracking system on Sourceforge.net or write a mail to the mailing list.

If you want to add a feature request, click here.

Changed lines 7-23 from:

If you want to add a feature request, click here.

to:

Please try to give us reliable instructions to reproduce the bug, so we can diagnose the cause. It would also help if you use a Sourceforge login so that you are notified by email if we need to ask you any questions about the bug report.

If Geany crashed/segfaulted, it will also help us if you can give us a backtrace with gdb:

  • Run gdb /path/to/geany
  • Type run followed by any command-line arguments you used with Geany when the bug occurred
  • Reproduce the segfault - it will be caught by gdb
  • Type bt and press enter if prompted

Send us everything from the run command - thanks.

Sometimes the backtrace is not useful if Geany was built without debug information, or useful information was removed by using -fomit-frame-pointer or by stripping the binary. In this case it would be great if you could get a backtrace from a fresh Geany build with appropriate debug flags:

  • make clean
  • ./configure CFLAGS=-g
  • Then build Geany with make, etc.

Note: a default source configure should include the -g debug flag.

July 09, 2006, at 12:42 PM by enrico - added %newwin%
Changed lines 3-5 from:

For the bug tracking system of SourceForge.net, click here.

If you want to add a feature request, click here.

to:

For the bug tracking system of SourceForge.net, click here.

If you want to add a feature request, click here.

July 09, 2006, at 12:42 PM by enrico - Created
Added lines 1-5:

If you found a bug in Geany or have a feature request, please use the bug tracking system on Sourceforge.net or write a mail to the mailing list.

For the bug tracking system of SourceForge.net, click here.

If you want to add a feature request, click here.