Backtrace Under Mac OS X - Revision history

Christian at 09:46, 27 October 2008

2008-10-27T09:46:48Z

← Older revision		Revision as of 09:46, 27 October 2008
Line 11:		Line 11:
	*If you have already compiled bluefish in local tree, and provided that the source files you want to backtrace have a <code>#define DEBUG</code> into them, which is not commented out, just perform steps 10-4, 10-5, 12bis, 13 and 14. You can check for the existence of the <code>#define DEBUG</code> lines by untaring the source file located in /sw/src. Copy it to your Desktop and perform step3.		*If you have already compiled bluefish in local tree, and provided that the source files you want to backtrace have a <code>#define DEBUG</code> into them, which is not commented out, just perform steps 10-4, 10-5, 12bis, 13 and 14. You can check for the existence of the <code>#define DEBUG</code> lines by untaring the source file located in /sw/src. Copy it to your Desktop and perform step3.
	*If you have already compiled bluefish in local tree, and the <code>#define DEBUG</code> lines do not exist or are commented out, move the source tarball to your desktop and perform steps 3, 4, 5, 6, 9, 10-2, 10-4, 10-5, 12bis, 13 and 14.		*If you have already compiled bluefish in local tree, and the <code>#define DEBUG</code> lines do not exist or are commented out, move the source tarball to your desktop and perform steps 3, 4, 5, 6, 9, 10-2, 10-4, 10-5, 12bis, 13 and 14.
	*If you want to return to normal compiling, remove from the info file<code>--with-debugging-output</code> in the <code>~[[ConfigParams]]</code> line or the whole line if it only contains this flag, and <code>-g</code> in the <code>[[SetCFLAGS]]</code> line or the whole line if it contains only that flag, delete the folder bluefishxxx in /sw/src and launch <code>fink rebuild bluefish</code>.		*If you want to return to normal compiling, remove from the info file<code>--with-debugging-output</code> in the <code>~ConfigParams</code> line or the whole line if it only contains this flag, and <code>-g</code> in the <code>SetCFLAGS</code> line or the whole line if it contains only that flag, delete the folder bluefishxxx in /sw/src and launch <code>fink rebuild bluefish</code>.
	1. Download the tarball from [http://bluefish.openoffice.nl/download.html], section Development Snapshots.		1. Download the tarball from [http://bluefish.openoffice.nl/download.html], section Development Snapshots.

Line 129:		Line 129:
	<code>cd /sw/src/bluefish-2003-10-16/bluefish-gtk2/</code><br>		<code>cd /sw/src/bluefish-2003-10-16/bluefish-gtk2/</code><br>
	Launch gdb with: <code>gdb src/bluefish</code><br>		Launch gdb with: <code>gdb src/bluefish</code><br>
	Then see details on [[~~DebuggingBluefish~~]] from Type r to start		Then see details on [[Debugging Bluefish]] from Type r to start

Christian at 09:46, 27 October 2008

2008-10-27T09:46:24Z

← Older revision		Revision as of 09:46, 27 October 2008
Line 1:		Line 1:
	=== Compiling the latest snapshots under Mac OS X		== Compiling the latest snapshots under Mac OS X ==

	~~====~~The following steps apply to:		The following steps apply to:
	* MacOS 10.2.8 or 10.3		* MacOS 10.2.8 or 10.3
	* Fink 0.15.0 and higher		* Fink 0.15.0 and higher
Line 7:		Line 7:
	* either gcc 3.1 or gcc 3.3		* either gcc 3.1 or gcc 3.3

	====Steps to perform:		===Steps to perform===
	*Note: Those steps are the necessary steps if you have not compiled bluefish in local tree previously.		*Note: Those steps are the necessary steps if you have not compiled bluefish in local tree previously.
	*If you have already compiled bluefish in local tree, and provided that the source files you want to backtrace have a <code>#define DEBUG</code> into them, which is not commented out, just perform steps 10-4, 10-5, 12bis, 13 and 14. You can check for the existence of the <code>#define DEBUG</code> lines by untaring the source file located in /sw/src. Copy it to your Desktop and perform step3.		*If you have already compiled bluefish in local tree, and provided that the source files you want to backtrace have a <code>#define DEBUG</code> into them, which is not commented out, just perform steps 10-4, 10-5, 12bis, 13 and 14. You can check for the existence of the <code>#define DEBUG</code> lines by untaring the source file located in /sw/src. Copy it to your Desktop and perform step3.

Christian at 09:45, 27 October 2008

2008-10-27T09:45:44Z

← Older revision		Revision as of 09:45, 27 October 2008
Line 2:		Line 2:

	====The following steps apply to:		====The following steps apply to:
	* [[MacOS]] 10.2.8 or 10.3		* MacOS 10.2.8 or 10.3
	* Fink 0.15.0 and higher		* Fink 0.15.0 and higher
	* Fink rsync (recommanded) or Fink cvs		* Fink rsync (recommanded) or Fink cvs
Line 14:		Line 14:
	1. Download the tarball from [http://bluefish.openoffice.nl/download.html], section Development Snapshots.		1. Download the tarball from [http://bluefish.openoffice.nl/download.html], section Development Snapshots.

	2. Don't let ~[[StuffItExpander]] expand it.		2. Don't let ~StuffItExpander expand it.

	3. Untar it::		3. Untar it::
Line 75:		Line 75:
	2 - Change the Source-MD5: line to have the new computed MD5 checksum.		2 - Change the Source-MD5: line to have the new computed MD5 checksum.

	3 - Check if you have a ~[[SourceDirectory]] line (if not already done):		3 - Check if you have a ~SourceDirectory line (if not already done):

	If you have one, change it to: <code>~[[SourceDirectory]]: bluefish-gtk2</code>		If you have one, change it to: <code>~SourceDirectory: bluefish-gtk2</code>

	If you don't have one, add a new line just after the Source-MD5 line, and type: <code>~[[SourceDirectory]]: bluefish-gtk2</code>		If you don't have one, add a new line just after the Source-MD5 line, and type: <code>~[[SourceDirectory]]: bluefish-gtk2</code>

Christian: New page: === Compiling the latest snapshots under Mac OS X ====The following steps apply to: * MacOS 10.2.8 or 10.3 * Fink 0.15.0 and higher * Fink rsync (recommanded) or Fink cvs * either gcc...

2008-10-26T19:56:19Z

New page: === Compiling the latest snapshots under Mac OS X ====The following steps apply to: * MacOS 10.2.8 or 10.3 * Fink 0.15.0 and higher * Fink rsync (recommanded) or Fink cvs * either gcc...

New page

=== Compiling the latest snapshots under Mac OS X

====The following steps apply to:
* [[MacOS]] 10.2.8 or 10.3
* Fink 0.15.0 and higher
* Fink rsync (recommanded) or Fink cvs
* either gcc 3.1 or gcc 3.3

====Steps to perform:
*Note: Those steps are the necessary steps if you have not compiled bluefish in local tree previously.
*If you have already compiled bluefish in local tree, and provided that the source files you want to backtrace have a <code>#define DEBUG</code> into them, which is not commented out, just perform steps 10-4, 10-5, 12bis, 13 and 14. You can check for the existence of the <code>#define DEBUG</code> lines by untaring the source file located in /sw/src. Copy it to your Desktop and perform step3.
*If you have already compiled bluefish in local tree, and the <code>#define DEBUG</code> lines do not exist or are commented out, move the source tarball to your desktop and perform steps 3, 4, 5, 6, 9, 10-2, 10-4, 10-5, 12bis, 13 and 14.
*If you want to return to normal compiling, remove from the info file<code>--with-debugging-output</code> in the <code>~[[ConfigParams]]</code> line or the whole line if it only contains this flag, and <code>-g</code> in the <code>[[SetCFLAGS]]</code> line or the whole line if it contains only that flag, delete the folder bluefishxxx in /sw/src and launch <code>fink rebuild bluefish</code>.
1. Download the tarball from [http://bluefish.openoffice.nl/download.html], section Development Snapshots.

2. Don't let ~[[StuffItExpander]] expand it.

3. Untar it::
Open the Terminal 
Move to the directory where you downloaded the tarball by typing: <code>cd ~nameofthedirectory</code> 
Press enter 
Assuming the name of the tarball is bluefish-2003-10-16.tar.bz2, type: <code>bzip2 -dc bluefish-2003-10-16.tar.bz2 | tar -xvf -</code> 
Press enter 

4. Enable debugging::
A new folder named bluefish-gtk2 has been created. 
Open it by double-clicking it, open the src folder inside it. 
Open the desired c file by double-clicking it and change it as follows: 
If you find a line: <code>/''' #define DEBUG '''/</code> near the top of the file, just remove the <code>/'''</code> and <code>'''/</code> on this line 
If this is not the case, add a new line just after the first <code>*/</code> and type: <code>#define DEBUG</code> 
Save the file

5. Tar the folder again::
Type in the terminal: <code>tar cf bluefish-2003-10-16.tar bluefish-gtk2</code> 
Press enter 
Move the tarball you downloaded elsewhere 
Type in the terminal: <code>bzip2 bluefish-2003-10-16.tar</code> 
Press enter in the terminal.

6. Copy the new tarball to /sw/src::
Type in the terminal: <code>sudo cp bluefish-2003-10-16.tar.bz2 /sw/src</code> 
Press enter 
Enter your password at the prompt

7. Check you gcc version with::
<code>gcc --v</code>

8. Copy Fink's bluefish.info and Fink's bluefish.patch files to your local tree (if not already done) with::
If you use gcc 3.1:

<code>sudo cp /sw/fink/10.2/unstable/main/finkinfo/editors/bluefish.* /sw/fink/10.2/local/main/finkinfo/</code>

If you use gcc 3.3 (be aware not to split the line):

<code>sudo cp /sw/fink/10.2-gcc3.3/unstable/main/finkinfo/editors/bluefish.* /sw/fink/10.2/local/main/finkinfo/</code>

If you only have a 10.3 tree:

<code>sudo cp /sw/fink/10.3/unstable/main/finkinfo/editors/bluefish.* /sw/fink/10.3/local/main/finkinfo/</code>

9. Compute the MD5 checksum for the snapshot with::
<code>md5 /sw/src/nameofthebluefishtarball</code>

10. Edit the info file with::
<code>sudo pico /sw/fink/10.2/local/main/finkinfo/bluefish.info</code> 
or: 
<code>sudo pico /sw/fink/10.3/local/main/finkinfo/bluefish.info</code>

1 - Change the Version: line to match the date in the tarball's name, i.e. if the name of the tarball is bluefish-2003-10-16.tar.bz2, change it to:

<code>Version: 2003-10-16</code>

2 - Change the Source-MD5: line to have the new computed MD5 checksum.

3 - Check if you have a ~[[SourceDirectory]] line (if not already done):

If you have one, change it to: <code>~[[SourceDirectory]]: bluefish-gtk2</code>

If you don't have one, add a new line just after the Source-MD5 line, and type: <code>~[[SourceDirectory]]: bluefish-gtk2</code>

4 - Add the g flags to the following line (create it if it does not exist) just under the ~[[SourceDirectory]] line:

<code>~[[SetCFLAGS]]: -g</code>

5 - Add the appropriate flag to the following line just under the above one:

<code>~[[ConfigureParams]]: --with-debugging-output</code>

11. Edit the patch info file with::
<code>sudo pico /sw/fink/10.2/local/main/finkinfo/bluefish.patch</code> 
or: 
<code>sudo pico /sw/fink/10.3/local/main/finkinfo/bluefish.patch</code>

Change the first two lines to have the date of the tarball's name in them, i.e. if the name of the tarball is bluefish-2003-10-16.tar.bz2, change them to:

<code>--- bluefish-2003-10-16/configure</code> 
<code>+++ bluefish-2003-10-16-patched/configure</code>

12. Check you Fink configuration with::
<code>cat /sw/etc/fink.conf</code>

The Trees: line should match the following: 
<code>Trees: local/main unstable/main unstable/crypto stable/main stable/crypto local/bootstrap</code>

If this is not the case, open the file with: 
<code>sudo pico /sw/etc/fink.conf</code>

and change the line accordingly.

12bis. (Only for version < 0.12) Remove any gnome-vfs2-ssl librairies as long as their versions are lower than 2.2::
Check the version with: 
<code>fink list -t -i gnome</code>

Remove the offending librairies (if any) with: 
<code>fink remove gnome-vfs2-ssl gnome-vfs2-ssl-dev gnome-vfs2-ssl-shlibs</code>

13. Rebuild the bluefish package::
For version < 0.13:
<code>fink -k rebuild bluefish</code> 
For version >=0.13: 
<code>fink -k rebuild bluefish-gnome2</code> if have GNOME2 installed 
<code>fink -k rebuild bluefish</code> otherwise 

14. Start gdb::
Launch X11 or XDarwin. Open an xterm. 
Move to the directory where the source is located by typing: 
<code>cd /sw/src/bluefish-2003-10-16/bluefish-gtk2/</code> 
Launch gdb with: <code>gdb src/bluefish</code> 
Then see details on [[DebuggingBluefish]] from Type r to start